Re: [PATCH 0/2] More ISO-8601 support
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Apr 14, 2020, 23:45 UTC
- Message-ID
- <20200414234504.GD2751707@camp.crustytoothpaste.net>
- In-Reply-To
- <cover.1586856398.git.congdanhqx@gmail.com>
On 2020-04-14 at 09:31:53, Đoàn Trần Công Danh wrote:
Show 15 quoted lines
> On 2020-04-14 00:03:24+0000, "brian m. carlson" <sandals@crustytoothpaste.net> wrote: > > git-commit(1) claims we support ISO 8601 format. However, our > > approxidate code misparses some dates with fractional seconds. > > We have never fully supported ISO-8601, those representation are > perfectly valid ISO-8601 (for 2020-04-14) but it would require > more code to parse correctly, perhap "tm_wday" and "tm_yday", > and mktime may help. > > 2020-W16-2 > --04-14 > 2020-105 > > I don't think not many people interested in those formats. > If someone really need them, we can get back to them later.
Yeah, I agree we don't need to support those. I would be happy if we said "RFC 3339", which is a more limited profile, and implemented that. The problem, as you alluded to (and I did as well in my original report), is that ISO 8601 provides a huge number of potential formats, most of which are not interesting for typical software.
-- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204