[thirdparty/git.git] / Documentation / date-formats.txt

DATE FORMATS
------------

The `GIT_AUTHOR_DATE`, `GIT_COMMITTER_DATE` environment variables
ifdef::git-commit[]
and the `--date` option
endif::git-commit[]
support the following date formats:

Git internal format::
	It is `<unix timestamp> <time zone offset>`, where `<unix
	timestamp>` is the number of seconds since the UNIX epoch.
	`<time zone offset>` is a positive or negative offset from UTC.
	For example CET (which is 1 hour ahead of UTC) is `+0100`.

RFC 2822::
	The standard email format as described by RFC 2822, for example
	`Thu, 07 Apr 2005 22:13:13 +0200`.

ISO 8601::
	Time and date specified by the ISO 8601 standard, for example
	`2005-04-07T22:13:13`. The parser accepts a space instead of the
	`T` character as well.
+
NOTE: In addition, the date part is accepted in the following formats:
`YYYY.MM.DD`, `MM/DD/YYYY` and `DD.MM.YYYY`.
Commit	Line	Data
788070a2 MV	1	DATE FORMATS
	2	------------
	3
47d81b5c	4	The `GIT_AUTHOR_DATE`, `GIT_COMMITTER_DATE` environment variables
788070a2 MV	5	ifdef::git-commit[]
	6	and the `--date` option
	7	endif::git-commit[]
	8	support the following date formats:
	9
	10	Git internal format::
0ffa154b	11	It is `<unix timestamp> <time zone offset>`, where `<unix
788070a2	12	timestamp>` is the number of seconds since the UNIX epoch.
0ffa154b	13	`<time zone offset>` is a positive or negative offset from UTC.
e2c20be5	14	For example CET (which is 1 hour ahead of UTC) is `+0100`.
788070a2 MV	15
	16	RFC 2822::
	17	The standard email format as described by RFC 2822, for example
	18	`Thu, 07 Apr 2005 22:13:13 +0200`.
	19
	20	ISO 8601::
	21	Time and date specified by the ISO 8601 standard, for example
	22	`2005-04-07T22:13:13`. The parser accepts a space instead of the
	23	`T` character as well.
	24	+
	25	NOTE: In addition, the date part is accepted in the following formats:
	26	`YYYY.MM.DD`, `MM/DD/YYYY` and `DD.MM.YYYY`.