| 1 | DATE FORMATS |
| 2 | ------------ |
| 3 | |
| 4 | The `GIT_AUTHOR_DATE` and `GIT_COMMITTER_DATE` environment variables |
| 5 | support the following date formats: |
| 6 | |
| 7 | Git internal format:: |
| 8 | It is `<unix-timestamp> <time-zone-offset>`, where |
| 9 | `<unix-timestamp>` is the number of seconds since the UNIX epoch. |
| 10 | `<time-zone-offset>` is a positive or negative offset from UTC. |
| 11 | For example CET (which is 1 hour ahead of UTC) is `+0100`. |
| 12 | + |
| 13 | It is safer to prepend the `<unix-timestamp>` with `@` (e.g., |
| 14 | `@0 +0000`), which forces Git to interpret it as a raw timestamp. This |
| 15 | is required for values less than 100,000,000 (which have fewer than 9 |
| 16 | digits) to avoid confusion with other date formats like `YYYYMMDD`. |
| 17 | |
| 18 | RFC 2822:: |
| 19 | The standard date format as described by RFC 2822, for example |
| 20 | `Thu, 07 Apr 2005 22:13:13 +0200`. |
| 21 | |
| 22 | ISO 8601:: |
| 23 | Time and date specified by the ISO 8601 standard, for example |
| 24 | `2005-04-07T22:13:13`. The parser accepts a space instead of the |
| 25 | `T` character as well. Fractional parts of a second will be ignored, |
| 26 | for example `2005-04-07T22:13:13.019` will be treated as |
| 27 | `2005-04-07T22:13:13`. |
| 28 | + |
| 29 | NOTE: In addition, the date part is accepted in the following formats: |
| 30 | `YYYY.MM.DD`, `MM/DD/YYYY` and `DD.MM.YYYY`. |
| 31 | |
| 32 | ifdef::git-commit[] |
| 33 | In addition to recognizing all date formats above, the `--date` option |
| 34 | will also try to make sense of other, more human-centric date formats, |
| 35 | such as relative dates like "yesterday" or "last Friday at noon". |
| 36 | endif::git-commit[] |