From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 12 Mar 2020 18:58:24 GMT
Subject: Re: [Feature request] "Hooks" for git log
Message-ID: <xmqqo8t1flin.fsf@gitster.c.googlers.com>
In-Reply-To: <558831584024173@sas1-438a02fc058e.qloud-c.yandex.net>

Konstantin Tokarev <annulen@yandex.ru> writes:

> I think it would be very useful if git log provided new option named e.g.
> --hook or --script, which would take script path as an argument.
> git log would follow it's normal way of operation, applying other filtering
> options it was given, however intstead of printing info on commit that
> matches filters, it invokes script with commit hash as an argument.
> Script can do whatever it needs with hash, including any git operations,
> can print commit info to log if needed, or print something else, or keep
> silence. If script returns non-zero, parent git log command terminates,
> otherwise it continues.

You do not need a hook for that, no?

 $ git log --format='%H' ...your other options here... |
   while read commit
   do
	... your "hook" that checks the $commit to see if
        ... it is "interesting" and shows or discard or whatever
        ... it does comes here
   done