Junio C Hamano <junkio@xxxxxxx> wrote: > Jeff King <peff@xxxxxxxx> writes: > > > BTW, is there some explanation why branch.*.merge specifies a _remote_ > > head? The following would make much more sense to me: > > > > [branch "master"] > > remote = origin > > merge = refs/remotes/origin/master > > Only *if* you store it in that tracking branch. The name the > other party gives _do_ matter to you anyway, because you have to > _know_ it to fetch. What it does NOT matter is if you use a > tracking branch, or if you do, which local tracking branch you > use to track it. My $0.02 USD (worth almost nothing these days!): I agree with Junio. branch.<n>.merge makes sense as the remote name. -- Shawn. - 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