# [BUG REPORT] --date argument doesn't validate dates 2 messages from 2020-04-22 to 2020-04-22. Participants: Yuri, brian m. carlson. Thread: https://gitlist.dev/t/53290 ## Yuri, 2020-04-22 20:40 Subject: [BUG REPORT] --date argument doesn't validate dates Message-ID: URL: https://gitlist.dev/e/d633919a-99a4-0b90-f355-66a17000f83f%40rawbw.com ``` For example, the following command accepts an invalid month "Dx" and an invalid year "20221" and sets the month to "Apr" and the year to "2020". Yuri $ git commit --amend --no-edit --date "Mon 20 Dx 20221 20:19:19 PST" [master 668e255] Initial  Date: Mon Apr 20 20:19:19 2020 -0700  1 file changed, 1 insertion(+)  create mode 100644 File [yuri@yv /usr/home/yuri/github/git-date]$ git log commit 668e255b54d08ed898e6d44f19954b2116d5a56c (HEAD -> master) Author: Yuri Date:   Mon Apr 20 20:19:19 2020 -0700     Initial ``` ## brian m. carlson, 2020-04-22 21:26 Subject: Re: [BUG REPORT] --date argument doesn't validate dates Message-ID: <20200422212633.GI6465@camp.crustytoothpaste.net> URL: https://gitlist.dev/e/20200422212633.GI6465%40camp.crustytoothpaste.net In-Reply-To: ``` On 2020-04-22 at 20:40:48, Yuri wrote: > For example, the following command accepts an invalid month "Dx" and an > invalid year "20221" and sets the month to "Apr" and the year to "2020". The --date argument accepts a wide variety of formats, including some formally specified ones, as well generalized handling through the "approxidate" approach. So it's designed to operate on formats that are not well understood and do the best it can with them. This also allows it do things like ignore the irrelevant word "ago" in "5 days ago" and still do the right thing. If you want to be sure that your date is uniformly understood, then the best approach is to either use the Git internal format or RFC 3339 (which is a profile of ISO 8601). -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 ```