| commit | 9deef088aec321e72955d6ededc9c9f62f083851 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Thu, 16 Feb 2023 00:42:25 +0000 (15 16:42 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 16 Feb 2023 01:34:46 +0000 (15 17:34 -0800) | ||
| tree | 0af5b84fcc639d7891e9e159c217df6e4ea4d445 | treesnapshot (tar.gz zip) |
| parent | 844ede312b4e988881b6e27e352f469d8ab80b2a | commitdiff |
rev-list: clarify git-log default date format
The documentation mistakenly said that the default format was
similar to RFC 2822 format and tried to specify it by enumerating
differences, which had two problems:
* There are some more differences from the 2822 format that are not
mentioned; worse yet
* The default format is not modeled after RFC 2822 format at all.
As can be seen in f80cd783 (date.c: add "show_date()" function.,
2005-05-06), it is a derivative of ctime(3) format.
Stop saying that it is similar to RFC 2822, and rewrite the
description to explain the format without requiring the reader to
know any other format.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The documentation mistakenly said that the default format was
similar to RFC 2822 format and tried to specify it by enumerating
differences, which had two problems:
* There are some more differences from the 2822 format that are not
mentioned; worse yet
* The default format is not modeled after RFC 2822 format at all.
As can be seen in f80cd783 (date.c: add "show_date()" function.,
2005-05-06), it is a derivative of ctime(3) format.
Stop saying that it is similar to RFC 2822, and rewrite the
description to explain the format without requiring the reader to
know any other format.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/rev-list-options.txt | diffblobblamehistory |