Petr Baudis <pasky@xxxxxxx> writes: > It's never been so easy before - I've written cg-admin-rewritehist, > which will execute your filters for each commit (which can rewrite the > tree contents, just the tree itself through the index, committer/author > information and commit message) while the script will obviously preserve > all the other information like merges, author/committer information etc. Hmph. The above description sounds like you are not allowing the user's custom script to drop existing parent (or graft a new one) while rewriting. I have not looked at how you are interfacing with user's custom script, but I sort-of expected you to throw a commit at it from older to newer (i.e. topo-order in reverse), along with the names of already re-written commit objects that are parents of taht commit, and have it build a rewritten commit and report its object name back to you. But it sounds like a useful tool in certain situations -- I sounded mildly negative last night, but after you gave an example of cleaning up a half-botched import, I changed my mind. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html