Junio C Hamano wrote: > Jonathan Nieder <jrnieder@xxxxxxxxx> writes: >> Could you give an example of breakage this configurability is designed >> to prevent? > > I think there is no "prevent" or "breakage"; the patch is to give people a > way to turn the feature on; without the configuration, "git merge" will > keep the traditional behaviour, no? Yes. One answer to my question is that a person might try git fetch git://some/random/repository branch git merge and at least for now it seems sensible to make that error out by default rather than doing something unexpected. In other words, another possible rule is "default to the last fetched branch" (FETCH_HEAD), so the intent behind running "git merge" without a branchname for the first time is not as obvious as I would hope. -- 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