From: Sam Vilain Date: Thu, 30 Oct 2008 16:44:41 GMT Subject: Re: Using the --track option when creating a branch Message-ID: <1225385081.19891.1.camel@maia.lan> In-Reply-To: <4909A7C4.30507@op5.se> On Thu, 2008-10-30 at 13:25 +0100, Andreas Ericsson wrote: > >> Ok, now I'm confused. The ONLY thing I want to prevent is the > >> "crossing of streams" issue. If I am on branch X and issue 'git > >> push', I want X, and ONLY X, to be pushed to the remote repository's X > >> branch --- I don't care if other branches are pushed to their > >> respective remote branches, as long as they don't get merged to X. > This particular bikeshed was painted a long time ago, with the consensus > going in favour of "git push" pushing all *matching* refspecs. I realise that - I just found it interesting that there was a user who explicitly expected this not to be the case. Which I think is reasonable, because it's what 'git pull' does. I myself have encountered many people who did not like the current default behaviour. I think far from "bikeshedding" this is quite an important part of the ui experience. Sam.