Re: inconsistent detached worktree handling: several bugs

From: martin f krafft <madduck@madduck.net>
Date: May 7, 2008, 18:06 UTC
Message-ID: <20080507180637.GA2282@lapse.madduck.net>
In-Reply-To: <8aa486160805070115k676b03a6s59d3a74d48d44254@mail.gmail.com>

also sprach Santi Béjar <sbejar@gmail.com> [2008.05.07.0915 +0100]:

Show 5 quoted lines

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

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

Why not?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"'oh, that was easy,' says Man, and for an encore goes on to prove
 that black is white and gets himself killed on the next zebra
 crossing."
            -- douglas adams, "the hitchhiker's guide to the galaxy"
 
spamtraps: madduck.bogus@madduck.net