Re: identical hashes on two branches, but holes in git log

2015-05-21 Thread Philippe De Muyter
On Tue, May 19, 2015 at 03:12:31PM -0700, Junio C Hamano wrote: Philippe De Muyter p...@macq.eu writes: On Tue, May 19, 2015 at 09:01:10AM -0700, Junio C Hamano wrote: Philippe De Muyter p...@macq.eu writes: Trying to understand, I have eventually done git log on my branch and on

Re: identical hashes on two branches, but holes in git log

2015-05-21 Thread Philippe De Muyter
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

Re: identical hashes on two branches, but holes in git log

2015-05-21 Thread Philip Oakley
From: Philippe De Muyter p...@macq.eu To: Junio C Hamano gits...@pobox.com Cc: git@vger.kernel.org; Jeff King p...@peff.net; John Keeping j...@keeping.me.uk Sent: Thursday, May 21, 2015 8:15 AM Subject: Re: identical hashes on two branches, but holes in git log On Tue, May 19, 2015 at

Re: identical hashes on two branches, but holes in git log

2015-05-21 Thread Philippe De Muyter
On Thu, May 21, 2015 at 08:58:35PM +0100, Philip Oakley wrote: From: Philippe De Muyter p...@macq.eu To: Junio C Hamano gits...@pobox.com Cc: git@vger.kernel.org; Jeff King p...@peff.net; John Keeping j...@keeping.me.uk Sent: Thursday, May 21, 2015 8:15 AM Subject: Re: identical hashes on

Re: identical hashes on two branches, but holes in git log

2015-05-21 Thread Junio C Hamano
Philippe De Muyter p...@macq.eu writes: So we trade correctness for speed :( No corretness is traded with anything else here. There are applications where topology matters and where it doesn't. When topology really matters (e.g. drawing the graph), the caller can choose to use --topo-order to

Re: identical hashes on two branches, but holes in git log

2015-05-20 Thread John Keeping
On Wed, May 20, 2015 at 03:13:59PM +0200, Philippe De Muyter wrote: My initial problem (still unresolved/unanswered) is that some commits that appeared between v3.14-rc1 and v3.14-rc2 (specifically 817c27a128e18aed840adc295f988e1656fed7d1) are present in v3.15, but not in my branch. I have

Re: identical hashes on two branches, but holes in git log

2015-05-20 Thread Philippe De Muyter
Hi John, On Wed, May 20, 2015 at 02:25:34PM +0100, John Keeping wrote: On Wed, May 20, 2015 at 03:13:59PM +0200, Philippe De Muyter wrote: My initial problem (still unresolved/unanswered) is that some commits that appeared between v3.14-rc1 and v3.14-rc2 (specifically

Re: identical hashes on two branches, but holes in git log

2015-05-20 Thread Jeff King
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