From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Date parsing
Date: Tue, 10 Jun 2008 17:31:07 +0200 [thread overview]
Message-ID: <bd6139dc0806100831y7a00a0f4sbc8dee9df7a8c16a@mail.gmail.com> (raw)
In-Reply-To: <Zx2uvEYSssjj9E0HrmUL8wYASyWX9L9w8LkR-gGRAmnD9isjoEeyKg@cipher.nrlssc.navy.mil>
On Tue, Jun 10, 2008 at 5:10 PM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> Take a look at match_multi_number in date.c
> European ordering is preferred when the separator is '.'
Ok, then I'll use . in the future, that's nice :).
> The timezone didn't change. One date is in daylight saving time, the other
> is not. The offset from GMT is different to reflect this.
As Hannes said, no bug there, my mistake.
>> What does the list think about this? Is this "normal"
>> behavior? If not, what (if anything) should we do about it?
>
> There will be flaws in any system that tries to automatically guess the
> format. If there is not already one, perhaps a statement should be added
> to the appropriate documentation describing how to ensure that european
> ordering is used to parse the date.
I think that it should bail out when it encounters "20-01-2008"
instead of automagically going for european notation. Even more
helpfull would be to inform the user that "20.01.2008" is the proper
notation.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-06-10 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:58 Date parsing Sverre Rabbelier
2008-06-10 15:07 ` Johannes Sixt
2008-06-10 15:27 ` Sverre Rabbelier
2008-06-10 15:10 ` Brandon Casey
2008-06-10 15:31 ` Sverre Rabbelier [this message]
2008-06-10 16:55 ` Linus Torvalds
2008-06-10 17:51 ` Sverre Rabbelier
2008-06-21 21:52 ` Stephan Beyer
2008-06-21 22:28 ` Linus Torvalds
2008-06-21 22:37 ` Linus Torvalds
2008-06-21 22:40 ` Stephan Beyer
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=bd6139dc0806100831y7a00a0f4sbc8dee9df7a8c16a@mail.gmail.com \
--to=alturin@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=sverre@rabbelier.nl \
/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