Johannes Schindelin writes: > Hi, > > On Mon, 5 Mar 2007, Michael Poole wrote: > >> I have not found a git workflow that makes me entirely happy, but I >> suspect I just don't know the magic words. > > So, what do you want to do? I want to have several local directories -- including build products and configuration files that are neither build products nor revision controlled -- that correspond to certain branches of one project. (Sometimes I have several trees for a single branch, to handle compile-time alternatives.) I do not much care whether there is a separate source tree for each of these or not. When I switch from working on one branch to another, I do not want file timestamps to be any later than the corresponding object was changed in the repository. When I change configuration options (including which branch(es) go to which remote(s)), I want to make that change in one $GIT_DIR rather than in one $GIT_DIR for each branch. As a lower priority, I would like a fetch on any of the branches to have results that are visible to all my local copies without more network traffic. The first two goals are neatly solved by having several local clones. The third and fourth are where I get lost. Michael Poole - 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