From: "Osipov, Michael (IN IT IN)" <michael.osipov@innomotics.com>
To: Junio C Hamano <gitster@pobox.com>,
"Osipov, Michael (IN IT IN)" <michael.osipov@innomotics.com>
Cc: git@vger.kernel.org
Subject: Re: bisect does not respect 'log.date'
Date: Wed, 13 Mar 2024 20:26:37 +0100 [thread overview]
Message-ID: <4e2b22fb-7496-4f67-a89f-9fcbffc73a1a@siemens.com> (raw)
In-Reply-To: <xmqq7ci6c7mn.fsf@gitster.g>
On 2024-03-13 19:24, Junio C Hamano wrote:
> "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
next prev parent reply other threads:[~2024-03-13 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 11:07 bisect does not respect 'log.date' Osipov, Michael (IN IT IN)
2024-03-13 18:24 ` Junio C Hamano
2024-03-13 19:26 ` Osipov, Michael (IN IT IN) [this message]
2024-03-25 20:27 ` Peter Krefting
2024-03-25 21:49 ` Junio C Hamano
2024-03-28 20:53 ` [RFC PATCH] bisect: Honor log.date Peter Krefting
2024-03-28 21:38 ` Eric Sunshine
2024-03-28 23:18 ` Peter Krefting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e2b22fb-7496-4f67-a89f-9fcbffc73a1a@siemens.com \
--to=michael.osipov@innomotics.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).