diff options
| author | Junio C Hamano <gitster@pobox.com> | 2012-02-02 21:41:43 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2012-02-04 07:11:32 (GMT) |
| commit | 2c733fb24c10a9d7aacc51f956bf9b7881980870 (patch) | |
| tree | 104b1c36ce3c47921f5d3fab81f5c7e7431a6d71 /git-sh-setup.sh | |
| parent | 116eb3abfe4f79907f701317c2d905868941fff7 (diff) | |
| download | git-2c733fb24c10a9d7aacc51f956bf9b7881980870.zip git-2c733fb24c10a9d7aacc51f956bf9b7881980870.tar.gz git-2c733fb24c10a9d7aacc51f956bf9b7881980870.tar.bz2 | |
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>
Diffstat (limited to 'git-sh-setup.sh')
| -rw-r--r-- | git-sh-setup.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-sh-setup.sh b/git-sh-setup.sh index 8e427da..015fe6e 100644 --- a/git-sh-setup.sh +++ b/git-sh-setup.sh @@ -200,7 +200,7 @@ get_author_ident_from_commit () { s/.*/GIT_AUTHOR_EMAIL='\''&'\''/p g - s/^author [^<]* <[^>]*> \(.*\)$/\1/ + s/^author [^<]* <[^>]*> \(.*\)$/@\1/ s/.*/GIT_AUTHOR_DATE='\''&'\''/p q |