From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: git-fast-import
Date: Tue, 6 Feb 2007 16:15:47 -0500 [thread overview]
Message-ID: <20070206211547.GB5820@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702061559160.13009@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
> I think you should call it something else than rfc2822. Because
> parse_date() accepts much more than just rfc2822. What about "cooked"?
It does accept a lot more than that, but straying away from rfc2822
gets into the grey areas of parse_date(). E.g. it matches crap such
as 'yyyy-mm-dd' or 'yyyy-dd-mm'. But that is completely ambiguous!
I don't really want to advertise that it is accepting non-RFC 2822
input here. I was thinking of doing an `iso` (yyyy-mm-dd hh:mm:ss)
format, which may just defer into parse_date(), but again encourage
the frontend to *only* feed that ISO style format.
--
Shawn.
next prev parent reply other threads:[~2007-02-06 21:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 2:31 git-fast-import Shawn O. Pearce
2007-02-06 3:18 ` git-fast-import Nicolas Pitre
2007-02-06 4:06 ` git-fast-import Nicolas Pitre
2007-02-06 5:48 ` git-fast-import Shawn O. Pearce
2007-02-06 16:35 ` git-fast-import Linus Torvalds
2007-02-06 16:56 ` git-fast-import Shawn O. Pearce
2007-02-06 17:20 ` git-fast-import Linus Torvalds
2007-02-06 18:53 ` git-fast-import Nicolas Pitre
2007-02-06 20:09 ` git-fast-import Shawn O. Pearce
2007-02-06 21:03 ` git-fast-import Nicolas Pitre
2007-02-06 21:15 ` Shawn O. Pearce [this message]
2007-02-06 21:42 ` git-fast-import Nicolas Pitre
2007-02-07 10:58 ` git-fast-import David Woodhouse
2007-02-06 6:12 ` git-fast-import Aneesh Kumar K.V
2007-02-06 6:18 ` git-fast-import Shawn O. Pearce
2007-02-07 4:55 ` git-fast-import Daniel Barkalow
2007-02-07 9:13 ` git-fast-import Karl Hasselström
2007-02-07 11:17 ` git-fast-import Johannes Schindelin
2007-02-07 22:55 ` git-fast-import Shawn O. Pearce
2007-02-07 23:55 ` git-fast-import Johannes Schindelin
2007-02-08 0:12 ` git-fast-import Shawn O. Pearce
2007-02-08 16:56 ` git-fast-import Linus Torvalds
2007-02-08 19:10 ` git-fast-import Shawn O. Pearce
2007-02-09 8:49 ` git-fast-import Karl Hasselström
2007-02-09 15:47 ` git-fast-import Linus Torvalds
2007-02-07 9:29 ` git-fast-import Raimund Bauer
2007-02-07 13:38 ` git-fast-import David Woodhouse
2007-02-06 9:28 ` git-fast-import Andy Parkins
2007-02-06 9:40 ` git-fast-import Shawn O. Pearce
2007-02-06 16:37 ` git-fast-import Linus Torvalds
2007-02-06 16:44 ` git-fast-import Shawn O. Pearce
2007-02-06 17:24 ` git-fast-import Linus Torvalds
2007-02-07 1:17 ` git-fast-import Horst H. von Brand
2007-02-07 2:50 ` git-fast-import Linus Torvalds
2007-02-07 5:53 ` git-fast-import Shawn O. Pearce
2007-02-07 9:21 ` git-fast-import Karl Hasselström
2007-02-07 22:18 ` git-fast-import Horst H. von Brand
2007-02-07 22:31 ` git-fast-import Jakub Narebski
2007-02-07 22:39 ` git-fast-import Linus Torvalds
2007-02-08 21:34 ` git-fast-import Johannes Schindelin
2007-02-07 5:46 ` git-fast-import Shawn O. Pearce
2007-02-07 4:45 ` git-fast-import Daniel Barkalow
2007-02-06 9:34 ` git-fast-import Jakub Narebski
2007-02-06 9:39 ` git-fast-import Shawn O. Pearce
2007-02-06 9:53 ` git-fast-import Jakub Narebski
2007-02-06 17:20 ` git-fast-import Shawn O. Pearce
2007-02-06 13:50 ` git-fast-import Alex Riesen
2007-02-06 17:43 ` git-fast-import Shawn O. Pearce
2007-02-06 18:02 ` git-fast-import Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2006-08-06 2:51 git-fast-import Jon Smirl
2006-08-06 3:40 ` git-fast-import Shawn Pearce
2006-08-06 4:09 ` git-fast-import Jon Smirl
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=20070206211547.GB5820@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.