From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2012, #02; Wed, 4)
Date: Thu, 5 Apr 2012 08:47:06 -0400 [thread overview]
Message-ID: <20120405124706.GA3921@sigill.intra.peff.net> (raw)
In-Reply-To: <7v8vib6pu8.fsf@alter.siamese.dyndns.org>
On Wed, Apr 04, 2012 at 04:26:39PM -0700, Junio C Hamano wrote:
> * jc/push-upstream-sanity (2012-04-03) 2 commits
> - [fixup] remove misguided "try to see if URLs are the same"
> - push: detect nonsense "upstream" check more carefully
>
> "git push $there" without refspec, when the current branch is set to push
> to a remote different from $there, used to push to $there using the
> upstream information to a remote unreleated to $there.
The patch produced by squashing those together looks good to me. Though
it might be worth getting input from people who use "upstream" (whether
it becomes the default or not) by re-posting the final patch under a
more obvious subject.
> This is necessary if we were to switch the push.default to 'current'.
I assume you meant "upstream" here.
-Peff
next prev parent reply other threads:[~2012-04-05 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 23:26 What's cooking in git.git (Apr 2012, #02; Wed, 4) Junio C Hamano
2012-04-05 12:47 ` Jeff King [this message]
2012-04-05 16:00 ` [PATCH] push: error out when the "upstream" semantics does not make sense Junio C Hamano
2012-04-05 18:43 ` Jonathan Nieder
2012-04-05 19:48 ` Junio C Hamano
2012-04-05 19:58 ` Jonathan Nieder
2012-04-05 20:01 ` Junio C Hamano
2012-04-05 20:23 ` Jonathan Nieder
2012-04-05 20:24 ` Matthieu Moy
2012-04-05 20:34 ` Junio C Hamano
2012-04-06 7:16 ` Matthieu Moy
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=20120405124706.GA3921@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).