Re: [PATCH RFC] cherry: support --abbrev option

From: Erik Faye-Lund <kusmabite@googlemail.com>
Date: Mar 15, 2010, 22:39 UTC
Message-ID: <40aa078e1003151539u2d1873bcy394063466c8e404b@mail.gmail.com>
In-Reply-To: <7vwrxdse24.fsf@alter.siamese.dyndns.org>

On Mon, Mar 15, 2010 at 6:13 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 15 quoted lines

> Erik Faye-Lund <kusmabite@googlemail.com> writes:
>
>> Switch to parse-options API while we're at it.
>>
>> Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
>> ---
>>
>> I sometimes find it useful to look at the commit-subject together with
>> the SHA-1s. Using --abbrev increases the chance that the lines fits on
>> an 80 character wide terminal, making the output easier to read.
>
> Even though "cherry" historically was meant to be a low-level helper for
> Porcelain scripts, I've seen people use it as the top-level UI, and I
> think what the patch tries to do makes sense.
>

I find it very useful. In fact, even the documentation seems to suggest to use it to find out if a patch is merged upstream, which doesn't sound very scriptish to me. So I think it has somehow exceeded it's original goal :)

-- 
Erik "kusma" Faye-Lund