From: Christian Neukirchen <chneukirchen@gmail.com>
To: git@vger.kernel.org
Subject: Re: git shortlog vs. stdin
Date: Tue, 15 Nov 2016 14:39:59 +0100 [thread overview]
Message-ID: <877f84dfps.fsf@gmail.com> (raw)
In-Reply-To: <20161115130418.GA28847@inner.h.apk.li> (Andreas Krey's message of "Tue, 15 Nov 2016 14:04:18 +0100")
Andreas Krey <a.krey@gmx.de> writes:
> Bug or feature?
Documented feature, but you're holding it wrong ;)
If no revisions are passed on the command line and either standard
input is not a terminal or there is no current branch, git shortlog
will output a summary of the log read from standard input, without
reference to the current repository.
(Note that you can use shortlog ala "git log --pretty=short | git shortlog")
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2016-11-15 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 13:04 git shortlog vs. stdin Andreas Krey
2016-11-15 13:39 ` Christian Neukirchen [this message]
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=877f84dfps.fsf@gmail.com \
--to=chneukirchen@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).