Re: git push default behaviour?

Junio C Hamano [off-list ref] writes:

I can send a message saying "There is a proposal to change the
default behaviour of 'git push' on the Git mailing list, and you may
be negatively affected if you do not see anything in the output from
'git config push.default' when such a change happens. On the other
hand, you may want to see the default behaviour to change. In either
case, please join the discussion to give us more data point and help
us decide the future of Git." to the kernel list. Anybody could, for
that matter.

Here's an attempt to an improved message. The first paragraph is here to
make sure people understand their opinion counts (before they stop
reading because it's too long). The rest explains the change and the way
to get involved:

---------- 8< ---------- 8< -----------

There is a proposal to change the default behaviour of 'git push'
on the Git mailing list. The goal of this message is to encourage you
to discuss it before it happens (or the change is aborted, depending
on the outcome of the discussion).

In the current setting (i.e. push.default=matching), 'git push' without
argument will push all branches that exist locally and remotely with
the same name. This is usually appropriate when a developer pushes to
his own public repository, but confusing if not dangerous when using a
shared repository. The proposal is to change the default to
'upstream', i.e. push only the current branch, and push it to the
upstream branch (the one 'git pull' would pull from). 'current' is
another candidate.

For more details on the behavior of Git with these values, read
the documentation about 'push.default' in 'man git-config'
(http://schacon.github.com/git/git-config.html).

You may be negatively affected when such a change happens if you
do not see anything in the output from 'git config push.default'
and if you rely on the fact that 'git push' pushes all your
matching branches. On the other hand, you may want to see the
default behaviour to change, especially if you are using shared
repositories. In either case, please join the discussion to give
us more data point and help us decide the future of Git.

To join the discussion, send your messages to: git@vger.kernel.org
You don't need to subscribe the list to post, and it's customary to
Cc: posters when replying on this list.
To view the current discussion, see this thread:
http://thread.gmane.org/gmane.comp.version-control.git/192547/focus=192694

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