blob: f1097fac69a6bbbe3c42b13a5a89dc185db526d5 [file] [log] [blame]
Junio C Hamanoae05fee2010-01-08 07:39:461DATE FORMATS
2------------
3
Junio C Hamano042f2142016-06-27 18:05:054The `GIT_AUTHOR_DATE`, `GIT_COMMITTER_DATE` environment variables
Junio C Hamanoae05fee2010-01-08 07:39:465ifdef::git-commit[]
6and the `--date` option
7endif::git-commit[]
8support the following date formats:
9
10Git internal format::
Junio C Hamanoe3acfb82013-11-12 23:22:5711It is `<unix timestamp> <time zone offset>`, where `<unix
Junio C Hamanoae05fee2010-01-08 07:39:4612timestamp>` is the number of seconds since the UNIX epoch.
Junio C Hamanoe3acfb82013-11-12 23:22:5713`<time zone offset>` is a positive or negative offset from UTC.
Junio C Hamano52b1cfb2016-12-20 00:18:3614For example CET (which is 1 hour ahead of UTC) is `+0100`.
Junio C Hamanoae05fee2010-01-08 07:39:4615
16RFC 2822::
17The standard email format as described by RFC 2822, for example
18`Thu, 07 Apr 2005 22:13:13 +0200`.
19
20ISO 8601::
21Time and date specified by the ISO 8601 standard, for example
22`2005-04-07T22:13:13`. The parser accepts a space instead of the
Junio C Hamanodd4c1782020-05-05 22:34:5423`T` character as well. Fractional parts of a second will be ignored,
24for example `2005-04-07T22:13:13.019` will be treated as
Junio C Hamano0beab6c2020-05-26 18:32:2525`2005-04-07T22:13:13`.
Junio C Hamanoae05fee2010-01-08 07:39:4626+
27NOTE: In addition, the date part is accepted in the following formats:
28`YYYY.MM.DD`, `MM/DD/YYYY` and `DD.MM.YYYY`.