Hi,

On Fri, 28 Sep 2007, Steffen Prohaska wrote:

quoted text
> On Sep 28, 2007, at 9:07 AM, Junio C Hamano wrote:
> 
> > 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?

If it changes behaviour, and there might be people relying on the old 
behaviour, we have to deprecate the old behaviour first.  With a nice 
warning so that people have a chance to adapt their setups.  And then, 
after a decent grace period, we can change it.

quoted text
> 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.

People have scripts and aliases to help them go through the day.  If one 
of those scripts or aliases stop working, that is called "break the 
existing setup".  ;-)

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html