On Wed, May 20, 2015 at 12:18:15PM -0400, Jeff King wrote: > On Wed, May 20, 2015 at 04:12:38PM +0200, Philippe De Muyter wrote: > > > After reading the man page of 'git log', should --topo-order not be the > > default log order ? > > The problem with --topo-order is that it has to traverse all of the > commits before starting output. So: > > $ time git log | head -1 > commit 64fb1d0e975e92e012802d371e417266d6531676 > > real 0m0.038s > user 0m0.032s > sys 0m0.008s > > $ time git log --topo-order | head -1 > commit 64fb1d0e975e92e012802d371e417266d6531676 > > real 0m4.247s > user 0m4.140s > sys 0m0.108s > > -Peff So we trade correctness for speed :( Is there a way to set topo-order as the default log order via git config ? Is topo-order already implemented as starting with the default order followed by an ancestor check or does it switch immediately to topological sort ? Philippe -- 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