From: Jeff King <peff@peff.net>
Date: Tue, 13 Mar 2012 21:35:23 GMT
Subject: Re: [RFC PATCH] push: start warning upcoming default change for push.default
Message-ID: <20120313213522.GA27752@sigill.intra.peff.net>
In-Reply-To: <7vehswljxi.fsf@alter.siamese.dyndns.org>

On Tue, Mar 13, 2012 at 06:17:13AM -0700, Junio C Hamano wrote:

> Pushing 'current' from a branch 'topic' forked from either 'master'
> or 'origin/master' will create a new branch 'topic' at the central
> repository. But that is straightforward and understandable. The user
> will see what happened in the feedback from the command, and there
> is no need for the user to be experienced enough to know the mapping
> of @{upstream} to understand why it happened.  "I am on 'topic' and
> I pushed, I created 'topic' there".  Very simple explanation exists.
> [...]
> That makes me suspect that 'current' might be a more appropriate
> default between the two. From that simple default, those in the
> "shared central repository" world can graduate to 'upstream' once
> they know what an 'upstream' is and how to take advantage of
> per-branch configuration.  Similarly, those in the "publish to be
> pulled" world would graduate to 'matching'.

Thanks for this explanation. When writing my last email, I had a gut
feeling about how "current" was a simpler choice, but I didn't quite
find the words to explain it. This paragraph (and the rest of the email)
covers what I was trying to say.

-Peff