Re: [PATCH 5/9] revert: add --ff option to allow fast forward when cherry-picking

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Paolo Bonzini
Date: Saturday, February 6, 2010 - 2:40 am

On 02/06/2010 12:11 AM, Christian Couder wrote:

I would still like to have a no-op --no-ff so that scripts that do rely 
on that can be future proofed (or also, scripts that do "git cherry-pick 
$blah -e COMMIT" could use --no-ff to avoid errors in case $blah 
contains --ff).

Paolo
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/9] add --ff option to cherry-pick, Christian Couder, (Fri Feb 5, 4:11 pm)
[PATCH 3/9] reset: refactor reseting in its own function, Christian Couder, (Fri Feb 5, 4:11 pm)
[PATCH 6/9] cherry-pick: add tests for new --ff option, Christian Couder, (Fri Feb 5, 4:11 pm)
[PATCH 8/9] rebase -i: use new --ff cherry-pick option, Christian Couder, (Fri Feb 5, 4:11 pm)
Re: [PATCH 0/9] add --ff option to cherry-pick, Junio C Hamano, (Fri Feb 5, 4:45 pm)
Re: [PATCH 5/9] revert: add --ff option to allow fast forw ..., Paolo Bonzini, (Sat Feb 6, 2:40 am)
Re: [PATCH 0/9] add --ff option to cherry-pick, Christian Couder, (Sat Feb 6, 8:27 am)