Re: inconsistent detached worktree handling: several bugs

From: Santi Béjar <sbejar@gmail.com>
Date: May 7, 2008, 19:20 UTC
Message-ID: <8aa486160805071220v50026bf9ga5a8ae4314bffadc@mail.gmail.com>
In-Reply-To: <20080507180637.GA2282@lapse.madduck.net>

On Wed, May 7, 2008 at 8:06 PM, martin f krafft <madduck@madduck.net> wrote:

Show 24 quoted lines

> also sprach Santi Béjar <sbejar@gmail.com> [2008.05.07.0915 +0100]:
>
> > 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.

Show 5 quoted lines

>
>  > - 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