From: Ted Pavlic <ted@tedpavlic.com>
To: Henk <henk_westhuis@hotmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Quick command to count commits
Date: Tue, 06 Jan 2009 14:55:23 -0500 [thread overview]
Message-ID: <4963B72B.8090406@tedpavlic.com> (raw)
In-Reply-To: <1231267896595-2118851.post@n2.nabble.com>
I doubt it's going to be much faster, but it's easier to type
git shortlog -s|numsum
I *think* that should give you the same number, and it forces git to do
more of the counting (rather than wc).
Strangely, on one repo that I test that on, I get slightly different
numbers from that command and yours. I'm not quite sure why (I guess
shortlog doesn't count all commits?).
--Ted
On 1/6/09 1:51 PM, Henk wrote:
>
> Hi,
>
> For GitExtensions (windows git ui) I need a command to count all commits. I
> now use this command:
> git.cmd rev-list --all --abbrev-commit | wc -l
>
> This works perfect but its very slow in big repositories. Is there a faster
> way to count the commits?
>
> Henk
--
Ted Pavlic <ted@tedpavlic.com>
prev parent reply other threads:[~2009-01-06 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 18:51 Quick command to count commits Henk
2009-01-06 18:55 ` Shawn O. Pearce
2009-01-06 19:30 ` Linus Torvalds
2009-01-06 19:55 ` Ted Pavlic [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=4963B72B.8090406@tedpavlic.com \
--to=ted@tedpavlic.com \
--cc=git@vger.kernel.org \
--cc=henk_westhuis@hotmail.com \
/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).