Re: [PATCH] log --oneline: put decoration at the end of the line

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 19, 2012, 23:34 UTC
Message-ID: <7vr4pxegec.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vr4pxg507.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> Jeff King <peff@peff.net> writes:
>
>> We should also consider briefly whether anybody is relying on --oneline
>> for machine parsing. I think "log --oneline" is fair game, but I wonder
>> if people calling "rev-list --decorate --oneline" should be considered.
>> It seems kind of unlikely to me, considering that the decorate output is
>> ambiguous to parse anyway (if you see parentheses, you cannot tell if it
>> is decorate output or part of the commit subject).
>
> Yeah, I do not think it is likely.  Among the in-tree scripts,
> git-stash does use rev-list --oneline but the purpose of the call
> exactly is to grab a human readable one line summary, and it will be
> happy with any change to make --oneline more human readble.

Having said that, one of my often used alias is

    [alias] recent = log --branches --oneline --no-merges --decorate --since=3.weeks

to help me see what topics in flight may potentially interact with an incoming patch, when deciding on which commit to base the patch on. Pushing the decoration at the end to let it fall off the right edge of the screen severely reduces the usefulness of it and defeats the point of using --decorate, at least for this use.

I could use --source instead, though, if it is not moved by the patch.