On Sun, Jul 08, 2007 at 05:37:22PM +0100, Johannes Schindelin wrote: > That is to be expected. After all, the first is a script. However, I > really have ask: how often per hour do you want to run that program? I have a project that needs some cleaning-up and I'd like to do it incrementally. I think I'll have to run it about a dozen times. > I am really unhappy that so much is talked about filtering out commits. > That is amost certainly not what you want in most cases. In particular, I > suspect that most users would expect the _changes_ filtered out by such a > command, which is just not true. I don't care about that either. I'm just mentioning it because it's mentioned in the git-filter-branch documentation (which you added). > The second is to rewrite the commit messages so that the hashes are > mapped, too. But that should be relatively easy, too: you can provide a > message filter, and you can use the provided "map" function. If this > seems to be what many people need, you can write a simple function and put > it into filter-branch for common use. It's not going to be me (as I sais, I don't like shell programming). skimo - To unsubscribe from this list: 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
