From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Caspar Zhang <caspar@casparzhang.com>,
git@vger.kernel.org, Gris Ge <fge@redhat.com>
Subject: Re: [BUG] incorrect search result returned when using git log with a future date parameter
Date: Wed, 30 Jan 2013 14:15:44 -0800 [thread overview]
Message-ID: <20130130221544.GA15680@google.com> (raw)
In-Reply-To: <7vsj5ijvei.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> 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. :)
Thanks,
Jonathan
next prev parent reply other threads:[~2013-01-30 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 11:30 [BUG] incorrect search result returned when using git log with a future date parameter Caspar Zhang
2013-01-30 19:57 ` Junio C Hamano
2013-01-30 22:15 ` Jonathan Nieder [this message]
2013-01-30 22:22 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2013-01-30 11:28 Caspar Zhang
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=20130130221544.GA15680@google.com \
--to=jrnieder@gmail.com \
--cc=caspar@casparzhang.com \
--cc=fge@redhat.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).