On Fri, 2012-11-09 at 16:04:31 +0100, Andreas Schwab wrote: > Ulrich Spörlein <uqs@xxxxxxxxxxxxx> writes: > > > Two questions: > > 1. Can we impose a stable ordering of the commits being recorded in a > > merge commit? Listing parents in chronological order or something like > > that. > > The order is determined by the order the refs are given to git merge (or > git commit-tree when using the plumbing). > > > 2. Why the hell is the commit hash dependent on the ordering of the > > parent commits? IMHO it should sort the set of parents before > > calculating the hash ... > > What would be the sort key? Trivially, the hash of the parents itself. So you'd always get ... parent 0000 parent 1111 parent aaaa parent ffff hth Uli -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html