From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jason Riedy <jason@acm.org>, git@vger.kernel.org
Subject: Re: Managing websites with git
Date: Tue, 02 Dec 2008 11:07:54 -0800 [thread overview]
Message-ID: <7vd4gapf91.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20081202165507.GA15826@coredump.intra.peff.net
Jeff King <peff@peff.net> writes:
> On Tue, Dec 02, 2008 at 10:55:34AM -0500, Jason Riedy wrote:
>
>> Ah, ok, thanks! Issuing a warning makes sense. I'm not sure if
>> denying such a push by default does...
> ...
> It shouldn't make you change how you work. At most, it will break an
> existing setup until you set receive.denycurrentbranch to false (again,
> if and when the default value changes). You can prepare for any such
> change now by pre-emptively setting the config value.
True.
But "pre-emptively" is a bit misleading. Please realize that the warning
is not about "this is a risky thing to do, you've been warned", but is
about "the behaviour to allow this may change in the future; if you rely
on it please set this config before that happens". We may end up not
flipping the default for a long time, but setting the config also has the
side effect of squelching the warning, so it never hurts to set it now.
next prev parent reply other threads:[~2008-12-02 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 16:30 Managing websites with git Felix Andersen
2008-11-30 17:07 ` David Bryson
2008-11-30 17:27 ` Jeff King
2008-12-02 0:46 ` Jason Riedy
2008-12-02 1:11 ` Jeff King
2008-12-02 15:55 ` Jason Riedy
2008-12-02 16:55 ` Jeff King
2008-12-02 19:07 ` Junio C Hamano [this message]
2008-12-02 1:36 ` Leo Razoumov
2009-01-03 21:29 ` Todd A. Jacobs
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=7vd4gapf91.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jason@acm.org \
--cc=peff@peff.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 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.