[BUG] git shortlog hangs in bare repo

Hi,

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.

Thanks,
Eugene

Hi,

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.

As far as I can tell, this problem is already fixed in the latest
upstream version- expect it to be fixed in the next release.

-- Ram

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.

On Sun, Apr 25, 2010 at 5:50 PM, Jonathan Nieder [off-list ref] wrote:

Hi Eugene,

Eugene Sajine wrote:

quoted

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.

Hi,

This is happening in Git 1.6.5.6.
The case here is that for the same project (same repo) in bare
shortlog is not working, in non-bare it is working instantaneously.

Thanks,
Eugene

Eugene Sajine wrote:

This is happening in Git 1.6.5.6.
The case here is that for the same project (same repo) in bare
shortlog is not working, in non-bare it is working instantaneously.

Thanks, that was helpful.  This is fixed by v1.7.1-rc0~157^2~1
(setenv(GIT_DIR) clean-up, 2010-02-06).  You can find v1.7.1 at
<http://www.kernel.org/pub/software/scm/git/>, for example[1].

Thanks, René.

Jonathan

[1] http://thread.gmane.org/gmane.linux.kernel/977720