author | Junio C Hamano <junkio@cox.net> | |
Wed, 5 Apr 2006 22:31:12 +0000 (15:31 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 5 Apr 2006 22:47:17 +0000 (15:47 -0700) | ||
commit | 38035cf4a51c48cccf6c5e3977130261bc0c03a7 | |
tree | f95e5d74177956489d01d4101ad02350ff019253 | tree | snapshot |
parent | 6cbd5d7d79f5751828397558e7c3611b048565fb | commit | diff |
date parsing: be friendlier to our European friends.
This does three things, only applies to cases where the user
manually tries to override the author/commit time by environment
variables, with non-ISO, non-2822 format date-string:
- Refuses to use the interpretation to put the date in the
future; recent kernel history has a commit made with
10/03/2006 which is recorded as October 3rd.
- Adds '.' as the possible year-month-date separator. We
learned from our European friends on the #git channel that
dd.mm.yyyy is the norm there.
- When the separator is '.', we prefer dd.mm.yyyy over
mm.dd.yyyy; otherwise mm/dd/yy[yy] takes precedence over
dd/mm/yy[yy].
Signed-off-by: Junio C Hamano <junkio@cox.net>
This does three things, only applies to cases where the user
manually tries to override the author/commit time by environment
variables, with non-ISO, non-2822 format date-string:
- Refuses to use the interpretation to put the date in the
future; recent kernel history has a commit made with
10/03/2006 which is recorded as October 3rd.
- Adds '.' as the possible year-month-date separator. We
learned from our European friends on the #git channel that
dd.mm.yyyy is the norm there.
- When the separator is '.', we prefer dd.mm.yyyy over
mm.dd.yyyy; otherwise mm/dd/yy[yy] takes precedence over
dd/mm/yy[yy].
Signed-off-by: Junio C Hamano <junkio@cox.net>
date.c | diff | blob | history |