Re: git cherry-pick --continue?

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 11, 2010, 23:13 UTC
Message-ID: <7vk4ujs6w0.fsf@alter.siamese.dyndns.org>
In-Reply-To: <76718491002111505u2935381erc376cea862e15801@mail.gmail.com>

Jay Soffian <jaysoffian@gmail.com> writes:

Show 6 quoted lines

> Blech, how is this an improvement? Why can't I just say "git
> cherry-pick --continue"?
>
> If I've still got the message in my terminal, it's no harder to use
> the SHA1. And if I've lost the message in my terminal, HEAD~23 is lost
> and I've got to dig the SHA1 out of my shell history anyway.

Maybe it doesn't look like an improvement to you, but I usually do my editing in other terminal and come back to the shell, so this is a huge improvement. It depends on the user.

I don't think Peff meant this change as the sole replacement for --cont anyway, so I don't understand why you are so upset about it.