Jonathan Nieder writes:
>> 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
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
Caspar Zhang writes:
> A date parsing function should parse _all dates with
> correctly format_, despite if it's an old date, or the date in the
> future.
When it is fed 2013-02-12, it is ambiguous and "approxidate" can and
should use whatever heuristics (including rejection of future) to
g
Hi there,
when I'm using the commit limit option `--before/--until` when doing
`git log` search, I meet a bug when the upper-bound date is 10days later
in the future. Here is an example:
$ date +%F
2013-01-30
$ git log --oneline --since=2013-01-01 --until=2013-02-01
$ git log --oneline --sin
Hi there,
when I'm using the commit limit option `--before/--until` when doing
`git log` search, I meet a bug when the upper-bound date is 10days later
in the future. Here is an example:
$ date +%F
2013-01-30
$ git log --oneline --since=2013-01-01 --until=2013-02-01
$ git log --oneline --sin
5 matches
Mail list logo
