From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Caleb Cushing <xenoterracide@gmail.com>,
git@vger.kernel.org
Subject: Re: git push origin error (1.6.3 new default functionality)
Date: Thu, 14 May 2009 09:37:39 +0200 [thread overview]
Message-ID: <4A0BCA43.9080408@drmicha.warpmail.net> (raw)
In-Reply-To: <20090514063157.GA10411@coredump.intra.peff.net>
Jeff King venit, vidit, dixit 14.05.2009 08:31:
> On Wed, May 13, 2009 at 11:54:20AM +0200, Michael J Gruber wrote:
[snip snip snip]
>> My main issue is the fact that we have a config variable (push.default)
>> which causes a different behaviour depending on whether it is unset or
>> set to its default (!) value. That is a completely new UI approach. We
>
> Well, it depends on how you think of the default. The default could be
> "matched-and-warn", and you are fixing it by setting it to "matched". :)
>
> -Peff
So, then we have a config variable which you can set to its default
value only by /unsetting/ it :)
In fact, I think that approach could be valuable in general, making git
more fool-proof for beginners while remaining efficient for the
regulars. As a new concept, to be taken up by "deny non-ff pushes",
"deny delation pushes", "pull without refspec" etc., I would like that.
In order to be useful, beginners should be able to rely on it, i.e.:
unless certain config is set, the git-gun should never go off when
pointed at users' own feet. Might be a worthy target for 1.7 (pun
semi-intended).
Michael
next prev parent reply other threads:[~2009-05-14 7:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 1:26 git push origin error (1.6.3 new default functionality) Caleb Cushing
2009-05-12 11:11 ` Michael J Gruber
2009-05-13 5:26 ` Caleb Cushing
2009-05-13 8:32 ` Jeff King
2009-05-13 8:44 ` Johannes Sixt
2009-05-13 9:03 ` Jeff King
2009-05-13 9:54 ` Michael J Gruber
2009-05-14 6:31 ` Jeff King
2009-05-14 7:37 ` Michael J Gruber [this message]
2009-05-13 18:37 ` Junio C Hamano
2009-05-14 3:30 ` Caleb Cushing
2009-05-14 4:44 ` Junio C Hamano
2009-05-14 5:29 ` Junio C Hamano
2009-05-14 8:57 ` Finn Arne Gangstad
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=4A0BCA43.9080408@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.net \
--cc=xenoterracide@gmail.com \
/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.