From: Jonathan Nieder <jrnieder@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [BUG] git shortlog hangs in bare repo
Date: Sun, 25 Apr 2010 16:50:42 -0500 [thread overview]
Message-ID: <20100425215042.GA25547@progeny.tock> (raw)
In-Reply-To: <u2i76c5b8581004221222ge8bb0b8cp55cb1f13d5f9692a@mail.gmail.com>
Hi Eugene,
Eugene Sajine wrote:
> I have tried to run this command in order to get some stats from the
> mainline bare repo. The result is that "shortlog" hangs for long
> period of time and nothing happens. At the same time git log works OK.
I’m a big shortlog fan, too, but I should mention a certain performance
characteristic: to sort its results by author, it has to build the whole
log before it can print anything to standard output at all. git log,
on the other hand, starts printing the most pertinent output right away.
Not sure that’s the problem, but thought I should mention it.
It would be nice to know what git version you are using, to be able to
check for relevant differences between your setup and mine.
Thanks for the report,
Jonathan
The most interesting recent change I could find is in v1.7.1-rc0~85^2
(shortlog: warn the user when there is no input, 2010-02-24). That is
for the no-repository case rather than the bare-repository one.
next prev parent reply other threads:[~2010-04-25 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 19:22 [BUG] git shortlog hangs in bare repo Eugene Sajine
2010-04-22 20:06 ` Ramkumar Ramachandra
2010-04-25 21:50 ` Jonathan Nieder [this message]
2010-04-26 18:03 ` Eugene Sajine
2010-04-26 18:25 ` Jonathan Nieder
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=20100425215042.GA25547@progeny.tock \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).