Re: git push (mis ?)behavior

From: Steffen Prohaska <prohaska@zib.de>
Date: Sep 28, 2007, 09:11 UTC
Message-ID: <9019207B-77A5-4595-8499-807DA0460EF0@zib.de>
In-Reply-To: <7vodfnqndc.fsf@gitster.siamese.dyndns.org>

On Sep 28, 2007, at 9:07 AM, Junio C Hamano wrote:

Show 8 quoted lines

> Steffen Prohaska <prohaska@zib.de> writes:
>
>> When "remote.<name>.push" is set I'd expect "git push" to
>> choose only the 'right' remote.<name>.push lines, that is
>> the lines that have the current branch as the local ref.
>
> That would break the existing setup so it would not fly as a
> default, although it could be added as an option.

Do you mean 'not now' or never, i.e. not in git 1.6?

What does 'break the existing setup' means? Pushing all branches that are configured in "remote.<name>.push" could be done by "git push <name>". This would be in the line with the idea that "git push" should only operate on the current branch and operations involving other local refs should be explicitly stated.

	Steffen