summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 72fdfb5)
raw | patch | inline | side by side (parent: 72fdfb5)
author | Junio C Hamano <junkio@cox.net> | |
Wed, 5 Apr 2006 05:57:15 +0000 (22:57 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 5 Apr 2006 06:00:18 +0000 (23:00 -0700) |
The comment associated with the date parsing code for three
numbers separated with slashes or dashes implied we wanted to
interpret using this order:
yyyy-mm-dd
yyyy-dd-mm
mm-dd-yy
dd-mm-yy
However, the actual code had the last two wrong, and making it
prefer dd-mm-yy format over mm-dd-yy.
Signed-off-by: Junio C Hamano <junkio@cox.net>
numbers separated with slashes or dashes implied we wanted to
interpret using this order:
yyyy-mm-dd
yyyy-dd-mm
mm-dd-yy
dd-mm-yy
However, the actual code had the last two wrong, and making it
prefer dd-mm-yy format over mm-dd-yy.
Signed-off-by: Junio C Hamano <junkio@cox.net>
date.c | patch | blob | history |
index 416ea579a3eb1dbc910817413f995556ad115b29..18a07103d8b5a018f8f424b0e44dbb89eff75905 100644 (file)
--- a/date.c
+++ b/date.c
@@ -257,10 +257,10 @@ static int match_multi_number(unsigned long num, char c, const char *date, char
break;
}
/* mm/dd/yy ? */
- if (is_date(num3, num2, num, tm))
+ if (is_date(num3, num, num2, tm))
break;
/* dd/mm/yy ? */
- if (is_date(num3, num, num2, tm))
+ if (is_date(num3, num2, num, tm))
break;
return 0;
}