Re: [PATCH] Add git-filter-branch

Hi,

On Wed, 6 Jun 2007, Johannes Sixt wrote:

It is more natural (for git users) to specify revision ranges like 
'master..next' instead. This makes it so. If no range is specified it 
defaults to 'HEAD'.

As a consequence, the new name of the filtered branch must be the first
non-option argument. All remaining arguments are passed to 'git rev-list'
unmodified.

I was really close to do this myself. But I thought there was a 
problem to infer the correct source branch.

But you're right, this is more gittish. (Consider that an ACK from me.)

Of course, it would be even more so if the target branch name was 
"filtered", overrideable by "--target <name>".

Ciao,
Dscho