On Sun, 05 Aug 2007 14:12:04 +0200 David Kastrup <dak@xxxxxxx> wrote: > Well, that is pretty much exactly what I find fascinating: that the > behavior is arbitrary and undocumented enough that one can't deduce it > either by logic or by recollection or by documentation, but just by > reading the code. > > Usually code is supposed to implement a design, but here it seems > rather like the design, if there is any, is to be abstracted from the > code. To me it's yet another example of bad UI design in Git. Git already had remote-tracking branches, which conceptually were relatively easy to explain. Instead of leveraging this foundation, and adding the ability for local branches to pick a default remote-tracking branch to use for merging, Git instead implemented direct remote tracking from local branches. After having read the thread Jeff mentioned earlier i'm still at a loss as to how this decision was justified. To make it even worse, it turns out that this command: $ git branch --track mybranch remote/branch Does _NOT_ tell git to setup mybranch to track remote/branch. Read that command line again and then scratch your head as to how anyone without deep Git knowledge is supposed to infer its real meaning without being told to read previous email threads etc. This also means the feature can't be used to say: $ git branch --track mybranch otherlocalbranch Being a fan of Git, it's frustrating to see that more weight is not paid to such UI concerns. Especially when the concern _was_ raised when the feature was first added. Sean - 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
