Jeremy Morton <jeremy@xxxxxxxxxxxx> writes: > On Thu, Mar 8, 2012 at 10:28 AM, Carlos Martín Nieto <cmn@xxxxxxxx> wrote: > > On Thu, 2012-03-08 at 10:13 +0000, Jeremy Morton wrote: > >> Right, so I guess I'm saying that the default value for push.default > >> should be upstream instead of matching... > > > > Any default is going to leave some people unhappy. If upstream is the > > right thing for you, then that's what you should use. Most questions I > > see about push not doing what the users expect would actually benefit > > from 'current'. 'matching' is a fairly safe default, as it won't try to > > push private branches or changes in private branches that track > > something upstream. > > But 'push --force' WILL try to push your (probably outdated) master > upstream, killing any changes there made since you last updated. That > alone is so dangerous it seems like reason enough to avoid it by > default. You can always configure server to refuse forced pushes. -- Jakub Narebski -- 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