From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-count-objects --all support
Date: Sat, 21 Jan 2006 19:48:19 -0800 [thread overview]
Message-ID: <7vd5ikhqik.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060122030215.GT28365@pasky.or.cz> (Petr Baudis's message of "Sun, 22 Jan 2006 04:02:15 +0100")
Petr Baudis <pasky@suse.cz> writes:
>> The point of counting objects is to see if it is time to repack,
>> so the warning is something I am quite hesitant to accept, even
>> with a suppression option.
>
> Then please change the command name - it is very confusing this way;
True. count-loose-objects would have been a good name, if it
were named that way from the beginning.
next prev parent reply other threads:[~2006-01-22 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 2:27 [PATCH] git-count-objects --all support Petr Baudis
2006-01-22 2:49 ` Junio C Hamano
2006-01-22 3:02 ` Petr Baudis
2006-01-22 3:48 ` Junio C Hamano [this message]
2006-01-22 3:03 ` Junio C Hamano
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=7vd5ikhqik.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).