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? Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- 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