From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Nicolas Pitre <nico@cam.org>,
git@vger.kernel.org
Subject: Re: [PATCH] pack.indexversion config option now defaults to 2
Date: Wed, 25 Jun 2008 08:14:53 +0200 [thread overview]
Message-ID: <20080625061453.GA32178@glandium.org> (raw)
In-Reply-To: <7viqvy59qr.fsf@gitster.siamese.dyndns.org>
On Tue, Jun 24, 2008 at 11:06:36PM -0700, Junio C Hamano wrote:
> Mike Hommey <mh@glandium.org> writes:
>
> > Wouldn't it be a good idea to add a warning in git update-server-info
> > when it detects pack.indexVersion is not 1, too ?
>
> Can you describe how that warning will help whom in the bigger picture?
>
> The way as I understand everybody runs "git update-server-info" is:
>
> * "git push" pushes into a publishing repository, then
> * "post-receive" (or "post-update") hook triggers "update-server-info".
>
> If you spit out a warning from update-server-info, it will be shown to the
> pusher over sideband, but this will not necessarily help the pusher, who
> may or may not have shell access to the repository.
There are also those that get the message to run update-server-info when
trying to clone over dumb protocol when the info/refs file is not
there... I actually didn't think about the post-receive hook.
Well, then, update-server-info could output the warning only if stderr
is a tty.
Mike
next prev parent reply other threads:[~2008-06-25 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 4:25 [PATCH] pack.indexversion config option now defaults to 2 Nicolas Pitre
2008-06-25 4:32 ` Linus Torvalds
2008-06-25 4:59 ` Junio C Hamano
2008-06-25 5:56 ` Mike Hommey
2008-06-25 6:06 ` Junio C Hamano
2008-06-25 6:14 ` Mike Hommey [this message]
2008-06-25 18:53 ` Nicolas Pitre
2008-06-25 18:58 ` Mike Hommey
2008-06-25 18:49 ` Nicolas Pitre
2008-06-25 19:19 ` 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=20080625061453.GA32178@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.