author | Junio C Hamano <gitster@pobox.com> | |
Thu, 2 Feb 2012 21:41:43 +0000 (13:41 -0800) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sat, 4 Feb 2012 07:11:32 +0000 (23:11 -0800) | ||
commit | 2c733fb24c10a9d7aacc51f956bf9b7881980870 | |
tree | 104b1c36ce3c47921f5d3fab81f5c7e7431a6d71 | tree | snapshot |
parent | 116eb3abfe4f79907f701317c2d905868941fff7 | commit | diff |
parse_date(): '@' prefix forces git-timestamp
The only place that the issue this series addresses was observed
where we read "cat-file commit" output and put it in GIT_AUTHOR_DATE
in order to replay a commit with an ancient timestamp.
With the previous patch alone, "git commit --date='20100917 +0900'"
can be misinterpreted to mean an ancient timestamp, not September in
year 2010. Guard this codepath by requring an extra '@' in front of
the raw git timestamp on the parsing side. This of course needs to
be compensated by updating get_author_ident_from_commit and the code
for "git commit --amend" to prepend '@' to the string read from the
existing commit in the GIT_AUTHOR_DATE environment variable.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The only place that the issue this series addresses was observed
where we read "cat-file commit" output and put it in GIT_AUTHOR_DATE
in order to replay a commit with an ancient timestamp.
With the previous patch alone, "git commit --date='20100917 +0900'"
can be misinterpreted to mean an ancient timestamp, not September in
year 2010. Guard this codepath by requring an extra '@' in front of
the raw git timestamp on the parsing side. This of course needs to
be compensated by updating get_author_ident_from_commit and the code
for "git commit --amend" to prepend '@' to the string read from the
existing commit in the GIT_AUTHOR_DATE environment variable.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/commit.c | diff | blob | history | |
date.c | diff | blob | history | |
git-sh-setup.sh | diff | blob | history | |
t/t3400-rebase.sh | diff | blob | history |