Jakub Narebski <jnareb <at> gmail.com> writes: > > On Thu, 21 Jul 2011, Fredrik Gustafsson wrote: > > On Thu, Jul 21, 2011 at 11:17:57AM -0700, Jakub Narebski wrote: > > > > Actually with git-new-workdir you can have multiple working > > > directories associated with single repository, by the way of symlinks. > > > > > > Note however that if you intend to *work* in those workdirs, they > > > better correspond to different branches... or you can mess something > > > heavy. > > > > It would be possible to use the .git-file feature here. Then symlinks are > > avoided and the solution is portable. > > Actually it wouldn't. Each new workdir has a separate HEAD and a > separate index; it is contents of .git that is symlinked, not .git > itself. > Is there any means to separate worktree info from the object repository? E.g., having a .git dir identical to that of a bare repo and a .git_workdir dir with the head, head logs, index and all what makes a nonbare repo different from a bare one? That might make it easier to transform a repo from bare to nonbare in addition to simplifying the logic of git-new-workdir. -- 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