Thread (9 messages) flat view 9 messages, 4 authors, 2016-06-15

Re: Using the --track option when creating a branch

From: Sam Vilain <hidden>
Date: 2016-06-15 22:45:33

On Thu, 2008-10-30 at 13:25 +0100, Andreas Ericsson wrote:
quoted
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help