git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] incorrect search result returned when using git log with a future date parameter

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 30, 2013, 22:22 UTC
Message-ID
<7v7gmujoqe.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130130221544.GA15680@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 9 quoted lines
>> When it is fed 2013-02-12, it is ambiguous and "approxidate" can and
>> should use whatever heuristics (including rejection of future) to
>> guess what the user wanted, but 2013-02-13 cannot be interpreted in
>> any other way, so we should parse it as such.
>
> FWIW, if you said 02/12/2013, I'd agree, but I've never seen someone
> using 2013-02-12 to mean December 2.
>
> So that suggests another possible tweak on top. :)

I think in the original context that triggered the "be more friendly to Europeans" discussion long time ago, some correlations between the delimiting characters (i.e. 'xxxx-xx-xx' vs 'xxxx.xx.xx' vs 'xxxx/xx/xx') and month-day ordering convention. I do not recall if we actually added that as a signal when disambiguating, though.

Previous: Jonathan Nieder
Message 4 of 4 in “[BUG] incorrect search result returned when using git log with a future date parameter”
  1. Caspar ZhangJan 30, 2013
  2. Junio C HamanoJan 30, 2013
  3. Jonathan NiederJan 30, 2013
  4. Junio C HamanoJan 30, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.