git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Approxidate with YYYY.MM

From
Brian Gernhardt <brian@gernhardtsoftware.com>
Date
May 9, 2011, 19:02 UTC
Message-ID
<CAE5FB52-0F90-4F21-828F-7E40ED596B33@gernhardtsoftware.com>
(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'm currently nearing finals in school, so lack the time for an RFC patch at the moment.
~~ Brian
Next: Michael J Gruber
Message 1 of 7 in “Approxidate with YYYY.MM”
  1. Brian GernhardtMay 9, 2011
  2. Michael J GruberMay 10, 2011
  3. Andreas EricssonMay 10, 2011
  4. Michael J GruberMay 10, 2011
  5. Victor EngmarkMay 10, 2011
  6. Michael J GruberMay 10, 2011
  7. Michael WittenMay 22, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.