Message-id: <87BE88BA-2827-4EDC-99BF-94026E604AB0@sb.org>
Date:	Mon, 19 Mar 2012 11:57:16 -0700
From:	Kevin Ballard <kevin@...org>
To:	Junio C Hamano <gitster@...ox.com>
Cc:	git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Please discuss: what "git push" should do when you do not say what
 to push?

I would love to see the default changed to 'upstream'. I've wanted this ever
since the push.default=tracking value was introduced. When introducing new
users to git, one of the first things I always tell them is to run

    git config --global push.default tracking

because it's far easier to explain how that behavior works than it is to
explain how the 'matching' behavior works, and it more closely aligns with
the way people (in my experience) typically use git.

-Kevin

On Mar 16, 2012, at 10:10 PM, Junio C Hamano wrote:

> 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. Also, if
> you think your friends and colleagues will be affected by this change,
> either positively or negatively, please tell them about this discussion.
> 
> 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@...r.kernel.org
> 
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists