On Tue, Apr 14, 2009 at 10:47 AM, Julian Phillips <julian@xxxxxxxxxxxxxxxxx> wrote: > Works fine for me. Are you sure you didn't have a typo in your original > git-new-workdir invocation? If so, could you supply: > > 1) the complete output of running git-new-workdir > 2) the output of "git rev-parse --git-dir" run in path/to/repo/.git > > Also, you shouldn't need to supply the .git, so "git new-workdir > path/to/repo newworkdirname" should also work, have you tried that? > git-new-workdir portage/ test /home/port/portdev/.bin/git-new-workdir: line 58: cd: /home/port/portdev/tree/portage .git: No such file or directory /home/port/portdev/tree/test cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory fatal: Not a git repository (or any of the parent directories): .git git-new-workdir portage/.git/ test /home/port/portdev/.bin/git-new-workdir: line 58: cd: /home/port/portdev/tree/portage/.git .: No such file or directory /home/port/portdev/tree/test cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory fatal: Not a git repository (or any of the parent directories): .git git rev-parse --git-dir portage/ fatal: Not a git repository (or any of the parent directories): .git cd portage/ /home/port/portdev/tree/portage slave-iv portage $ git rev-parse --git-dir . .git . git-new-workdir . ../test/ << seems to work too. -- Caleb Cushing http://xenoterracide.blogspot.com -- 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