git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Caleb Cushing <xenoterracide@gmail.com>, git@vger.kernel.org
Subject: Re: git push origin error (1.6.3 new default functionality)
Date: Wed, 13 May 2009 11:37:52 -0700	[thread overview]
Message-ID: <7vprec4znj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4A09594F.4040603@drmicha.warpmail.net> (Michael J. Gruber's message of "Tue\, 12 May 2009 13\:11\:11 +0200")

Michael J Gruber <git@drmicha.warpmail.net> writes:

> 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.

Thanks for saying this concisely, and saving me from repeating this.

> 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.

It is not weird at all.  Although I am still not convinced (and I suspect
some old timers are not either), the default could change in the future
and by setting it to 'matching', you will protect yourself from such a
change.  Consider it a vaccination ;-)

  parent reply	other threads:[~2009-05-13 18:38 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
2009-05-13 18:37   ` Junio C Hamano [this message]
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=7vprec4znj.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --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 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).