Re: git push default behaviour?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

> Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes:
>
>> 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:
>
> Sounds OK from a cursory read, except for a few minor details.
>
> Thanks.  Nitpicks follow.

I'm taking them all. Here's the result:

---------- 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 may be 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 branch
'git pull' would pull from. Another candidate is 'current'; this pushes
only the current branch to the remote branch of the same name.

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 default that 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.

What has been discussed so far can be seen in this thread:
http://thread.gmane.org/gmane.comp.version-control.git/192547/focus=192694
Previous relevant discussions include:
http://thread.gmane.org/gmane.comp.version-control.git/123350/focus=123541
http://thread.gmane.org/gmane.comp.version-control.git/166743

To join the discussion, send your messages to: git@xxxxxxxxxxxxxxx
The list accepts messages from non-subscribers, and you do
not have to ask "please Cc me, I am not subscribed", as it's
customary to Cc: posters when replying on this list.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]