Re: bisect does not respect 'log.date'

From: Osipov, Michael (IN IT IN) <michael.osipov@innomotics.com>
Date: Mar 13, 2024, 19:26 UTC
Message-ID: <4e2b22fb-7496-4f67-a89f-9fcbffc73a1a@siemens.com>
In-Reply-To: <xmqq7ci6c7mn.fsf@gitster.g>

On 2024-03-13 19:24, Junio C Hamano wrote:

Show 15 quoted lines

> "Osipov, Michael (IN IT IN)" <michael.osipov@innomotics.com> writes:
> 
>> An oversight or bug?
> 
> Neither, i.e. WAI, I would say.
> 
> The configuration variable log.date is about "git log" and its
> documentation makes no promises how "git bisect" may or may not be
> affected.
> 
> Having said that, I think it is not unreasonable for you to make it
> a feature request to add bisect.dateformat or whatever.  The only
> interesting part from the output being the exact commit object name
> the problem bisects to, I personally would not see it a high priority
> feature request, though.

Interesting thought, but that also means that "git show" misbehaves because it respects "log.date" and there is no "show.date". I still think that consistency shouldn't be obeyed. I'd be happy if someone could consider this improvement.

Michael