All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: Approxidate with YYYY.MM
Date: Tue, 10 May 2011 08:35:46 +0200	[thread overview]
Message-ID: <4DC8DCC2.8050208@drmicha.warpmail.net> (raw)
In-Reply-To: <CAE5FB52-0F90-4F21-828F-7E40ED596B33@gernhardtsoftware.com>

Brian Gernhardt venit, vidit, dixit 09.05.2011 21:02:
> (This is in response to a discussion on #parrot.)
> 
> Rakudo (https://github.com/rakudo/rakudo/) uses tags of the form
> YYYY.MM for their monthly releases.  When we were attempting to find
> the cause of a slowdown, somewhat was trying to find what commits
> occurred after the 2011.01 release with "git log --after=2011.01".
> His mistake was pointed out but this led to the confusion of why this
> was parsed as "May 1 2011" instead of "Jan 1 2011".  Shouldn't
> date.c:match_multi_number() parse something with only two numbers as
> a beginning of month instead of allowing it to pass through to the
> generic parsing?

I just don't think there is a format like that. There is dd.mm.[yy]yy
and apparently also yyyy.mm.dd, but without leading zeros in mm for the
latter. Our date parser also takes "." for a space so that you don't
need to quote a space ("1.day.ago"). I can see the logic behind parsing
2011.01 as January 2011, but it's a stretch from the existing formats:

http://en.wikipedia.org/wiki/Calendar_date#Date_format

> I'm currently nearing finals in school, so lack the time for an RFC
> patch at the moment.

Good luck :)

Michael

  reply	other threads:[~2011-05-10  6:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:02 Approxidate with YYYY.MM Brian Gernhardt
2011-05-10  6:35 ` Michael J Gruber [this message]
2011-05-10  6:54   ` Andreas Ericsson
2011-05-10  7:08     ` Michael J Gruber
     [not found]   ` <964517.31047.1305010481774.JavaMail.trustmail@mail1.terreactive.ch>
2011-05-10  7:40     ` Victor Engmark
2011-05-10  8:36       ` Michael J Gruber
2011-05-22 17:10         ` Michael Witten

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=4DC8DCC2.8050208@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=brian@gernhardtsoftware.com \
    --cc=git@vger.kernel.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.