From: Michael J Gruber <git@drmicha•warpmail.net>
To: Caleb Cushing <xenoterracide@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: git push origin error (1.6.3 new default functionality)
Date: Tue, 12 May 2009 13:11:11 +0200 [thread overview]
Message-ID: <4A09594F.4040603@drmicha.warpmail.net> (raw)
In-Reply-To: <81bfc67a0905111826y779555cer6679da11db787ab1@mail.gmail.com>
Caleb Cushing venit, vidit, dixit 12.05.2009 03:26:
> in the past git push origin would just push all matching branches to
> the remote, and it worked. the new error says that's still the
> default. The new functionality is nice, but is it really the git way
> to yell at you if you haven't explicitly set the default? I think the
> default should remain the default, and it should continue to work
> without yelling at you for not explicitly setting it. if you want to
> change it that's fine.
>
\begin{rambling}
It is a fall-out from the new user friendliness initiative. Watch out
for parentheses:
it's ( (new user) friendliness ), not ( new (user friendliness) ).
The principle is: if a user is about to do something which is documented
but might not have been intended we throw a half-screen full of text at
them. The idea is that it is virtually impossible to grasp at a glance
from that much text what happened, so that the user is forced to read
the whole text. edugit, so to say.
\end{rambling}
Seriously, we had that discussion when the feature (change of default
behaviour) and warning were introduced, so it's too late for a change.
But it's never too late to do
git config --global push.default matching
and be done with it.
The weird thing is that the default is "matching" already. But it makes
a difference whether you have set the variable to its default value
explicitly or not. No man page says so (neither git-push nor
git-config), and I can't think of other variables with such a behaviour.
Michael
next prev parent reply other threads:[~2009-05-12 11:11 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 [this message]
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
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=4A09594F.4040603@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=xenoterracide@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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