| commit | aff2e7c0677d882690213d7ddea4a868f8b18325 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 21 Jun 2013 18:08:02 +0000 (21 11:08 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 21 Jun 2013 18:16:31 +0000 (21 11:16 -0700) | ||
| tree | 4fa951af039fdcad298f686d68f2a83eda570861 | treesnapshot (tar.gz zip) |
| parent | 11667316d0dc455131b3898fdd29fe080b5ae4e0 | commitdiff |
t6003: add --author-date-order test
Tweak the --topo/date-order test vector a bit and mark the author
dates of two commits (a2 and a3) earlier than their own committer
dates, making them much older than other commits that are made on
parallel branches to simulate the case where a long running topic
was rebased recently.
They will show up as recent in the --date-order output due to their
timestamps, but they appear a lot later in the --author-date-order
output, even though their committer timestamp says otherwise.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Tweak the --topo/date-order test vector a bit and mark the author
dates of two commits (a2 and a3) earlier than their own committer
dates, making them much older than other commits that are made on
parallel branches to simulate the case where a long running topic
was rebased recently.
They will show up as recent in the --date-order output due to their
timestamps, but they appear a lot later in the --author-date-order
output, even though their committer timestamp says otherwise.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t6003-rev-list-topo-order.sh | diffblobblamehistory |