From: "Jan Krüger" <jk@jk.gs>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Nicolas Pitre <nico@fluxnic.net>,
Johan Herland <johan@herland.net>,
git@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
ftpadmin@kernel.org
Subject: Re: git gc and kernel.org
Date: Wed, 21 Oct 2009 12:21:02 +0200 [thread overview]
Message-ID: <20091021122102.0793295e@perceptron> (raw)
In-Reply-To: <4ADEC0DB.4000104@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> wrote:
> $ git gc --auto --quiet
> Auto packing your repository for optimum performance. You may also
> run "git gc" manually. See "git help gc" for more information.
> [...]
> [*] Skipping the hint to "run git gc manually" would even be good in
> this case, because the hint pertains the remote repository, not the
> one from which "git push" was issued.
I agree with your suggestions. On the same note, while we're already
changing the message, it might make sense to change it to "Auto packing
the repository [...]".
Jan
next prev parent reply other threads:[~2009-10-21 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 7:00 git gc and kernel.org H. Peter Anvin
2009-10-20 7:48 ` Junio C Hamano
2009-10-20 7:51 ` H. Peter Anvin
2009-10-20 8:54 ` Johan Herland
2009-10-20 18:46 ` Nicolas Pitre
2009-10-20 21:02 ` Junio C Hamano
2009-10-20 21:16 ` Nicolas Pitre
2009-10-20 21:56 ` [PATCH] receive-pack: run "gc --auto" and optionally "update-server-info" Junio C Hamano
2009-10-21 0:21 ` Nicolas Pitre
2009-10-21 6:25 ` git gc and kernel.org Johannes Sixt
2009-10-21 7:23 ` Junio C Hamano
2009-10-21 7:39 ` Junio C Hamano
2009-10-21 8:05 ` Johannes Sixt
2009-10-21 10:21 ` Jan Krüger [this message]
2009-10-21 22:30 ` [PATCH 1/2] gc --auto --quiet: make the notice a bit less verboase Junio C Hamano
2009-10-21 22:32 ` [PATCH 2/2] receive-pack: run "gc --auto --quiet " and optionally "update-server-info" Junio C Hamano
2009-10-20 9:08 ` git gc and kernel.org Mikael Magnusson
2009-10-21 1:00 ` H. Peter Anvin
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=20091021122102.0793295e@perceptron \
--to=jk@jk.gs \
--cc=ftpadmin@kernel.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hpa@zytor.com \
--cc=j.sixt@viscovery.net \
--cc=johan@herland.net \
--cc=nico@fluxnic.net \
/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).