git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Garry Dolley <gdolley@arpnetworks.com>, git@vger.kernel.org
Subject: Re: git-shortlog hangs on bare repo without --bare option
Date: Wed, 27 Aug 2008 15:19:03 -0700	[thread overview]
Message-ID: <7vvdxmm78o.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <48B5C9E4.4030807@lsrfire.ath.cx> (René Scharfe's message of "Wed, 27 Aug 2008 23:40:52 +0200")

René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:

> Garry Dolley schrieb:
>> I didn't see this happen with git 1.5.x, but if you do git-shortlog on a bare 
>> repo, without specifying --bare, the command will seemingly hang indefinitely.
>
> FWIW, I tried git 1.5.0 and it hangs, too.  Which exact version did work
> for you?  Could you, based on it, bisect the commit that introduced this
> behaviour?
>
> As a workaround, you can use "git log | git shortlog".

It is not a workaround.  Shortlog can work as a filter to "git log", but
if you give revs to work on, e.g. "git shortlog -s -n v1.5.6.5.." or "git
shortlog HEAD", it can generate the log and feed to itself.

Somehow it (perhaps incorrectly, I did not look at the command line input)
judging that your command line is telling it not to do the log generation
itself but instead you will feed the log from its standard input, which
happens to be your terminal.  So another workaround would be to type the
series of log messages ;-)

  parent reply	other threads:[~2008-08-27 22:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 19:52 git-shortlog hangs on bare repo without --bare option Garry Dolley
2008-08-27 20:32 ` Junio C Hamano
2008-08-27 21:21   ` Garry Dolley
2008-08-27 21:40 ` René Scharfe
2008-08-27 22:15   ` Garry Dolley
2008-08-27 22:19   ` Junio C Hamano [this message]
2008-08-27 22:41     ` Junio C Hamano
2008-08-27 23:09       ` Junio C Hamano
2008-08-27 23:16       ` Junio C Hamano
2008-08-27 23:30         ` Jeff King
2008-08-28  4:56           ` Junio C Hamano
2008-08-28  7:16         ` Nguyen Thai Ngoc Duy

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=7vvdxmm78o.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=gdolley@arpnetworks.com \
    --cc=git@vger.kernel.org \
    --cc=rene.scharfe@lsrfire.ath.cx \
    /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).