Josef Weidendorfer <Josef.Weidendorfer@xxxxxx> writes: > In a previous discussion, you talked about switching to > the new behavior (ie. getting rid of this "first set of > branches" rule) when there is at least one branch.*.merge > setting in the config file. > > Unfortunately I can not see an easy way to check this with > repo-config, as there is no wildcard support for keys > (Ok, I can do a list of keys and grep). I think --get-regexp is what you want -- see my "patch for discussion". > I think it is better to provide an option > "pull.do-not-follow-the-first-set-of-branches-rule". > And we should make this the default after init-db or clone. Yes, but the problem is that old timers do make new clones. pull.i-like-the-first-set-of-branches in ~/.gitconfig is the only thing I can think of but that is too ugly and is already on the slippery slope of user.expert configuration which I do not think we want. - 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