[+Nguyán ThÃi Ngác Duy, who is currently working on improving/fixing how git handles worktree detection] On Mon, Nov 1, 2010 at 18:22, Paul Drews <paul.drews@xxxxxxxxx> wrote: > I'm observing an unexpected error from "git rebase" run from the directory > containing the ".git" directory: > > $ git --version > > git version 1.7.3.GIT > (includes up to commit ca2090 from git repository at > http://www.kernel.org/pub/scm/git/git.git) > > $ mkdir wherefilesare > $ mkdir wheregitis > $ cd wherefilesare > $ echo "Here is a line from the original" > myfile.txt > $ cd ../wheregitis > $ git init > $ git config core.worktree /absolute/path/to/wherefilesare/ > $ git add . > $ git commit > $ git branch mybranch > $ git checkout mybranch > $ vim ../wherefilesare/myfile.txt > $ git add . > $ git commit > $ git checkout master > $ vim ../wherefilesare/myfile.txt > $ git add . > $ git commit > $ git checkout mybranch > $ git rebase master > > fatal: /usr/libexec/git-core/git-rebase cannot be used without a working tree. > > Since I'm in the directory containing ".git" at this point, the ".git" directory > and the worktree can be unambiguously found. ÂOther commands besides "git > rebase" work. ÂI would expect "git rebase" to work as well. ÂIs this a bug or an > unreasonable expectation on my part? Sounds like a bug. -- Cheers, Sverre Rabbelier -- 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