Hi, On Mon, 4 Feb 2008, Brandon Casey wrote: > Johannes Schindelin wrote: > > > BTW just to tell you why I am so excited with your patch: I have a > > patch to git-branch in my tree, which implements the git-new-workdir > > functionality (it's a patch to git-branch, not git-checkout, mainly > > because git-checkout is no builtin yet). > > Are you planning something that works like: > > $ cd <my_repo> > $ git branch > * master > other_branch > $ git checkout --new-workdir ../<other_work_dir> other_branch > > (not sure how it would work using git-branch). Something like this, yes. In my local version of git, you can say "git branch --new-workdir=../bla new-branch [branch-point]". > Have you thought about using git-clone instead? Briefly. But this is not about cloning the repository. It is about having an additional working directory for the current repository. > It seems a good fit but would require a new option to specify a branch > to checkout (which I believe is a requested feature for clone). It is an often-requested feature for clone, but we have "clone -n" for now, and nobody seemed to care deeply enough to actually do something about it. But really, clone is something different. I _want_ the original repository to know that there is another working directory. Ciao, Dscho - 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
