From: Junio C Hamano <gitster@pobox•com>
To: Mitchel Humpherys <mitch.special@gmail•com>
Cc: git@vger•kernel.org, jonas@bernoul•li
Subject: Re: Why is --graph --max-count=n so much slower than --graph HEAD~n..?
Date: Tue, 20 May 2014 15:50:43 -0700 [thread overview]
Message-ID: <xmqq61l0rrng.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vnkwd2f8ayea.fsf@mitchelh-linux.qualcomm.com> (Mitchel Humpherys's message of "Tue, 20 May 2014 15:17:01 -0700")
Mitchel Humpherys <mitch.special@gmail•com> writes:
> I've noticed that --max-count doesn't seem to speed up `git log --graph'
> computation time.
AFAIK, --graph wants to compute the whole history and the max-count
only affects the output phase after --graph does its computation.
Besides, "log --max-count=n" and "log HEAD~n.." compute completely
different things, so the comparison is apples and oranges.
next prev parent reply other threads:[~2014-05-20 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 22:17 Why is --graph --max-count=n so much slower than --graph HEAD~n..? Mitchel Humpherys
2014-05-20 22:50 ` Junio C Hamano [this message]
2014-05-21 0:13 ` Mitchel Humpherys
2014-05-21 0:24 ` 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=xmqq61l0rrng.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jonas@bernoul$(echo .)li \
--cc=mitch.special@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox