Re: git push default behaviour?

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: git push default behaviour?

From: Matthieu Moy <hidden>
Date: 2016-06-15 22:53:15

Carlos Martín Nieto [off-list ref] writes:
On Thu, 2012-03-08 at 10:13 +0000, Jeremy Morton wrote:
quoted
Right, so I guess I'm saying that the default value for push.default
should be upstream instead of matching...
Any default is going to leave some people unhappy. If upstream is the
right thing for you, then that's what you should use. Most questions I
see about push not doing what the users expect would actually benefit
from 'current'. 'matching' is a fairly safe default, as it won't try to
push private branches or changes in private branches that track
something upstream.
There were some discussions about changing the default, and I thought
people agreed that 'upstream' was a better default value for
push.default:

  http://permalink.gmane.org/gmane.comp.version-control.git/167149

it needs to be done with a sane migration path, however, and I guess no
one stepped in to start the process (but I may have missed some further
discussions).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: git push default behaviour?

From: demerphq <hidden>
Date: 2016-06-15 22:53:15

On 8 March 2012 12:54, Matthieu Moy [off-list ref] wrote:
Carlos Martín Nieto [off-list ref] writes:
quoted
On Thu, 2012-03-08 at 10:13 +0000, Jeremy Morton wrote:
quoted
Right, so I guess I'm saying that the default value for push.default
should be upstream instead of matching...
Any default is going to leave some people unhappy. If upstream is the
right thing for you, then that's what you should use. Most questions I
see about push not doing what the users expect would actually benefit
from 'current'. 'matching' is a fairly safe default, as it won't try to
push private branches or changes in private branches that track
something upstream.
There were some discussions about changing the default, and I thought
people agreed that 'upstream' was a better default value for
push.default:

 http://permalink.gmane.org/gmane.comp.version-control.git/167149

it needs to be done with a sane migration path, however, and I guess no
one stepped in to start the process (but I may have missed some further
discussions).
From the point of view of new users the current default is sub-optimal
and confusing. I actually find the current default an odd choice, as I
personally have *never* wanted to push all the branches at once, nor
have I ever seen a colleague want to do that.

cheers,
Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help