From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add git-count-packs, like git-count-objects.
Date: Sat, 28 Oct 2006 16:28:29 +0200 [thread overview]
Message-ID: <ehvpcs$20j$2@sea.gmane.org> (raw)
In-Reply-To: 20061028065143.GA14607@spearce.org
Shawn Pearce wrote:
> Junio C Hamano <junkio@cox.net> wrote:
>> Shawn Pearce <spearce@spearce.org> writes:
>>
>> > Now that we are starting to save packs rather than unpacking into
>> > loose objects its nice to have a way to list the number of current
>> > packs and their total size. This can help the user in deciding
>> > when its time to run `git repack -a -d`.
>>
>> Why not just do "ls -lh $GIT_OBJECT_DIR/pack/pack-*.pack"???
>
> Because whatever we decide to use to make a pack 'active' may not
> be that simple.
>
> Whatever. It was clearly a very tiny patch put together quickly
> before dinner tonight, perhaps not worth including at this point.
> Lets see what comes out of the other pack oriented discussion first.
Perhaps to nod add yet another command to already large set, rename
git-count-objects to git-count end enhance it to count both loose objects
and packs (or not, and use git-count-objects name).
BTW what does "garbage:" in git-count-objects -v mean? And in what units
git-count-objects -v returns "size:" (git-count-objects says "kilobytes",
why git-count-objects -v doesn't do the same)?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-28 14:28 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 [this message]
2006-11-02 9:30 ` Nguyen Thai Ngoc Duy
2006-11-03 12:53 ` Jakub Narebski
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='ehvpcs$20j$2@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).