Re: inconsistent detached worktree handling: several bugs

On Wed, May 7, 2008 at 8:06 PM, martin f krafft [off-list ref] wrote:

also sprach Santi Béjar [off-list ref] [2008.05.07.0915 +0100]:

quoted

I don't know if it resolves all the issues, but:

 >
 > - If run outside of the working copy => equivalent to run it from the
 > top of the wc.
 >   (for the normal case it just fails)

 This is not what the output of git-status suggests:

 lapse:~|master|.fgits/zsh.git% git status                                #1,801

# On branch master
 # Changed but not updated:
 #   (use "git add <file>..." to update what will be committed)
 #
 #       modified:   ../../.zsh/zshrc/30_aliases
 #

no changes added to commit (use "git add" and/or "git commit -a")

 If, what you said were the case, it'd be .zsh/zshrc/30_aliases.
 ../.. is the setting of core.worktree.

So it is run inside the worktree ( $workingdir/.fgits/zsh ) and the
repository is inside the worktree.

 > - It is not recommended (supported?) to have the repository inside
 > the working directory (unless it is .git, of course)

 Why not?

I read it in this list but I don't find it now. Maybe because of the
special handling of .git does not apply to an arbitrary path.

Santi