Re: RFC: Adding an option to log-like commands to call an external command for each revision

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 12, 2010, 21:25 UTC
Message-ID: <7vmxrmd57r.fsf@alter.siamese.dyndns.org>
In-Reply-To: <AANLkTi=WokEQMDc92SoWXPJW67dy0q79WW9RajrBHRx3@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 6 quoted lines

> I just like the UI of having each commit "pop up" where I can either
> page up/down within the commit, or dismiss it with "q" and go to the
> next one.
>
> You can't do both of those in a pager, up/down goes across commits,
> and "q" quits the whole pager.

I would throw this not into the incomplete scriptability category but into the "user does not know how to use his pager" category. With "/^commit .*" you can not only advance to the next commit with "/<RET>", you can go back to the previous one with "?<RET>", and keep going in the same direction with "n".

>>> Maybe we should have something like:
>>>
>>>     git log --for-each=less a..b

If anything that shouldn't be an option to "log", but to "rev-list", as you are aiming for scriptability. But

    git rev-list --for-each='cmd that takes commit as its argument'

wouldn't be much of an improvement over "git rev-list | xargs -n1 'cmd'" pipeline from the _scriptability_ point of view.

So no.