From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin-commit: add --date option
Date: Wed, 2 Dec 2009 22:40:34 +0100 [thread overview]
Message-ID: <20091202214034.GD31763@genesis.frugalware.org> (raw)
In-Reply-To: <7vaay1gt0z.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Wed, Dec 02, 2009 at 09:55:24AM -0800, Junio C Hamano <gitster@pobox.com> wrote:
> I should have mentioned ones with more importance in real-life before
> referring you to the amusing ones: US and European dates.
>
> date.c::match_multi_number() groks these:
>
> mm/dd/yy[yy] (US)
> dd.mm.yy[yy] (European)
As far as I see these are also about approxidate() as well. But thanks
for the ISO number, now I have enough info to add documentation about
it. Patch is coming soon... ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-12-02 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 0:27 [PATCH] builtin-commit: add --date option Miklos Vajna
2009-12-02 17:11 ` Miklos Vajna
2009-12-02 17:35 ` Junio C Hamano
2009-12-02 17:55 ` Junio C Hamano
2009-12-02 21:40 ` Miklos Vajna [this message]
2009-12-02 19:24 ` Jeff King
2009-12-02 20:33 ` Miklos Vajna
2009-12-02 19:26 ` Jeff King
2009-12-02 19:38 ` Junio C Hamano
2009-12-02 21:07 ` Miklos Vajna
2009-12-02 22:16 ` [PATCH 1/2] " Miklos Vajna
2009-12-02 22:16 ` [PATCH 2/2] Document date formats accepted by parse_date() Miklos Vajna
2009-12-02 22:33 ` Nanako Shiraishi
2009-12-02 22:42 ` Jeff King
2009-12-02 22:54 ` Junio C Hamano
2009-12-02 23:49 ` [PATCH 2/2 v2] " Miklos Vajna
2009-12-02 22:12 ` [PATCH] builtin-commit: add --date option Miklos Vajna
2009-12-02 22:22 ` Jeff King
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=20091202214034.GD31763@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--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).