> From: Brandon Casey [mailto:casey@xxxxxxxxxxxxxxx] > My take on it... > > If you want to have _multiple_different_ branches checked out > from the _same_ repository, and do development in all of > them, then git-new-workdir is the right choice. > Yes, that's precisely what we want to do. So according to your experience, we're making the right choice then. > If you want to have the _same_branch_ checked out in multiple > work directories, then cloning with -s is what you want. In > this case I assume development will be performed in the > original repo, and the clones will do a pull to update. > Ok, for us this would probably be rare, but good to know. > Personally, I have found the git-new-workdir script to > satisfy any need which caused me to even think about cloning > with -s. I am hoping the functionality of git-new-workdir > will be folded into git porcelain at some point (ahem J Schindelin). > We'd like that too ;-) > -brandon > > Cheers, Craig -- 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
