On Wed, May 29, 2013 at 12:57 AM, Johannes Sixt [off-list ref] wrote:
Am 5/29/2013 8:39, schrieb Martin von Zweigbergk:
quoted
+# a---b-----------c
+# \ \
+# d-------e \
+# \ \ \
+# n---o---w---v
+# \
+# z
quoted
+#TODO: make all flavors of rebase use --topo-order
+test_run_rebase success 'e n o' ''
+test_run_rebase success 'e n o' -m
+test_run_rebase success 'n o e' -i
As test_commit offers predictable timestamps, I think you can work around
this discrepancy by generating commits n and o before e. (That is not a
solution--just a workaround that depends on the current
implementation--because the order in which parents of a merge are listed
is unspecified.)
I actually liked it as documentation of the current inconsistency and
with an explicit TODO.
I have addressed the remainder of your comments in this and the next
message. Thanks again.