All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Philippe De Muyter <phdm@macq.eu>
Cc: John Keeping <john@keeping.me.uk>, git@vger.kernel.org
Subject: Re: identical hashes on two branches, but holes in git log
Date: Wed, 20 May 2015 12:18:15 -0400	[thread overview]
Message-ID: <20150520161815.GA12521@peff.net> (raw)
In-Reply-To: <20150520141238.GA13990@frolo.macqel>

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

  reply	other threads:[~2015-05-20 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 13:29 identical hashes on two branches, but holes in git log Philippe De Muyter
2015-05-19 16:01 ` Junio C Hamano
2015-05-19 21:47   ` Philippe De Muyter
2015-05-19 22:12     ` Junio C Hamano
2015-05-21  7:15       ` Philippe De Muyter
2015-05-21 19:58         ` Philip Oakley
2015-05-21 20:37           ` Philippe De Muyter
2015-05-20  7:39     ` Christian Couder
2015-05-19 23:39 ` Jeff King
2015-05-20 13:13   ` Philippe De Muyter
2015-05-20 13:25     ` John Keeping
2015-05-20 14:12       ` Philippe De Muyter
2015-05-20 16:18         ` Jeff King [this message]
2015-05-21  7:05           ` Philippe De Muyter
2015-05-21 16:45             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150520161815.GA12521@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=john@keeping.me.uk \
    --cc=phdm@macq.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.