Using git filter-branch to remove commits by their commit message?

Write a script to remove lines with Redmine #555.

Write a script to remove lines with Redmine #555: #! /bin/sh mv $1 $1. $$ grep -v 'Redmine #555' $1 rm -f $1.

$$ Of course you can do that however you want (eg echo a script of commands to ed). Then launch your rebase with EDITOR set to your script: EDITOR=/path/to/script git rebase -i REVISION Of course it still won't be guaranteed to complete -- there may be errors during the rebase caused by leaving out revisions. You can still fix them and git rebase --continue manually.

– machineghost Jan 4 '11 at 22:26 The help for --commit-filter specifically mentions that skip_commit leaves out the commit but not the changes and says to use git-rebase instead. Filter-branch considers your revisions as a sequence of states and allows you to permute each commit, but the changes to not propagate to the children. Rebase considers your revisions as a stack of patches and any modification midstream does propagate to future revisions.

But that can cause failures which is why it can't be fully automatic. – Ben Jackson Jan 4 '11 at 22:35 Ahhhhhhh. Thanks!

– machineghost Jan 5 '11 at 19:30.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.