From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 19 Nov 2007 08:35:52 GMT
Subject: Re: [PATCH 2/2] push: Add '--current', which pushes only the current branch
Message-ID: <7vk5oeocnr.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <53F12F4D-73C5-446E-9A97-9D2D4CA9DF9F@zib.de>

Steffen Prohaska <prohaska@zib.de> writes:

> What's left is a new switch "--current".  Less code, easy
> to explain.

But won't that force the "current" people always type that from
the command line, as your previous point was that your earlier
patch to say "remote.$there.push = HEAD" does not work that way?
If that configuration works as expected, then I'd 100% agree
that we would not need push.defaultRefs.  Either you do not have
"push" at all if your preference is --matching, or you do have
"push = HEAD" if your preference is --current.  But if it
doesn't (which was what I gathered from your earlier response),
having a configuration would help them, wouldn't it?

Changing the default, if it will ever happen, is _NOT_ to help
people who are already using git and want "current" NOW.  The
current users cannot be helped _unless_ we switch overnight, but
that is not an option as it introduces a regression to people's
established workflow.

Changing the default is to help new users who will come in the
future, if majority of the existing users find --current easier
to explain to new people _they_ need to train.