Junio C Hamano wrote:
> Felipe Contreras <felipe.contre...@gmail.com> writes:
> > Signed-off-by: Felipe Contreras <felipe.contre...@gmail.com>
> > ---
> > builtin/revert.c | 2 +
> > sequencer.c | 136
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++--
> > sequencer.h | 2 +
> > t/t3500-cherry.sh | 32 +++++++++++++
> > 4 files changed, 169 insertions(+), 3 deletions(-)
> "git cherry-pick" should help maintaining notes just like amend and
> rebase, but how should this interact with notes.rewrite.<command>,
> where the command is capable of doing this without an explicit
> option once you tell which notes need to be maintained?
> Thomas Rast Cc'ed as he has been the primary force behind this line
> of "notes" usability.
> It probably is not sensible to carry over note from a reverted
> commit to its revert, but I didn't immediately spot how the patch
> does this only for cherry-pick but not for revert (the codepath in
> do_pick_commit() is shared between them, no?).
The option is enabled from the UI, and only 'git cherry-pick' has the
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html