All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: Caleb Cushing <xenoterracide@gmail.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org
Subject: Re: git push origin error (1.6.3 new default functionality)
Date: Wed, 13 May 2009 10:44:33 +0200	[thread overview]
Message-ID: <4A0A8871.6080107@viscovery.net> (raw)
In-Reply-To: <20090513083203.GA25058@sigill.intra.peff.net>

Context: This is about the warning that a plain "git push" produces if no
push refspec are configured. The default behavior is to push matching
branches.

Jeff King schrieb:
> Or are you proposing to still change the default behavior, but drop the
> warning whose aim is to inform people about the impending change? In
> that case, I think you should address the concerns that arose from
> previous changes in default behavior (and which this warning is meant to
> address), and propose an alternate plan for making the transition more
> smooth.

Unfortunately, the case with this warning is not that "simple" because it
is not about a planned change of the default behavior, but about a default
behavior that may be unexpected for newbies (see the release notes of
1.6.3). I *can* understand that Caleb is upset by the warning, since he's
comfortable with the (current and future) default behavior. But I don't
know what to do in cases like these.

-- Hannes

  reply	other threads:[~2009-05-13  8:46 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 [this message]
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=4A0A8871.6080107@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --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.