El 27/9/2007, a las 21:22, Junio C Hamano escribió:
What you would want to change is the fallback behaviour for
unconfigured "remote.<name>.push". I think it is sensible to
have an option to make it push only the current branch. I am
not sure if it is sensible to make that the default (and
introduce --matching option to get the current behaviour) at
this point in 1.5.X series, but from the general usability point
of view, I would not object to demote 'matching' to optional and
make 'current only' the default in 1.6.X or later.
Thoughts?
I'd certainly welcome this change for two reasons:
1. It makes the behaviour more conservative (that is, harder to do
something destructive and irreversible) by using the more limited
scope by default. If you make a mistake and see that you really meant
to push all matching branches then you can just do the push again
with that switch; compare that to the situation now where if you
accidentally push all matching branches when you only wanted to push
the current branch then there's no way for you to "unpush".
2. Mental baggage from working with SVK (where "push" means merge
changes back to the branch the current branch previously branched
from, and "pull" means merge changes into the current branch from the
branch you previously branched from). At least for me and I suspect
for many others the "current only" default in 1.6 or latter would be
less "surprising" than the current behaviour can be.
Cheers,
Wincent
-
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
