From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: 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 00:39:14 -0700 [thread overview]
Message-ID: <7vaazl8acd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vzl7l8b1y.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed\, 21 Oct 2009 00\:23\:53 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Johannes Sixt <j.sixt@viscovery.net> writes:
>
>> Junio C Hamano schrieb:
>>> + if (auto_gc) {
>>> + const char *argv_gc_auto[] = { "gc", "--auto", NULL };
>>> + run_command_v_opt(argv_gc_auto, RUN_GIT_CMD);
>>
>> Am I correct that this will produce progress output? If git-daemon runs
>> receive-pack, then this output will go to the syslog. Do we care?
>
> We do, and we don't want that. Thanks for spotting.
>
> Would adding "--quiet" to the mix be enough?
Actually I don't know. This originally came from "we _could_ add gc and
update-server-info to hundreds of post-receive hooks, but any repository
hosting site that holds many central repositories will exactly have the
same issue, so why not do this internally", so it may make sense to do
exactly the same thing as what we do to the output from hooks. What do we
do to them now? stdout-to-stderr?
next prev parent reply other threads:[~2009-10-21 7:39 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 [this message]
2009-10-21 8:05 ` Johannes Sixt
2009-10-21 10:21 ` Jan Krüger
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=7vaazl8acd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ftpadmin@kernel.org \
--cc=git@vger.kernel.org \
--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).