From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add git-count-packs, like git-count-objects.
Date: Fri, 03 Nov 2006 13:53:08 +0100 [thread overview]
Message-ID: <eife2p$qqq$1@sea.gmane.org> (raw)
In-Reply-To: fcaeb9bf0611020130r70ed6f4cnf67586deff36452e@mail.gmail.com
Nguyen Thai Ngoc Duy wrote:
> On 10/28/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> Perhaps to not to add yet another command to already large set, rename
>> git-count-objects to git-count, and enhance it to count both loose objects
>> and packs (or not, and use git-count-objects as command name).
>
> Oh if so, I'd suggest git-stats over git-count :-)
Or even git-db-stats (as companion to git-db-init).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-11-03 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 4:00 [PATCH] Add git-count-packs, like git-count-objects Shawn Pearce
2006-10-28 4:11 ` Junio C Hamano
2006-10-28 6:51 ` Shawn Pearce
2006-10-28 14:28 ` Jakub Narebski
2006-11-02 9:30 ` Nguyen Thai Ngoc Duy
2006-11-03 12:53 ` Jakub Narebski [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='eife2p$qqq$1@sea.gmane.org' \
--to=jnareb@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).