Re: [long] worktree setup cases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> wrote:

> > Example:
> >
> >  repo           /tmp/git/.git
> >  starting cwd   /tmp/git/.git/objects/pack
> 
> OK it's considered a bare repo, so no worktree.

Not necessarily: if config tells it's a non-bare repo, we could
assume, the worktree is where core.worktree tells (which per
default is "../" - relative to gitdir).

But currently it seems to be implemented as you said: running
git-status from within gitdir tells:

    "fatal: This operation must be run in a work tree"

That's not really bad, but sometimes a bit inconvenient.

> Also the "relative to $GIT_DIR" may be confusing. If $GIT_DIR points
> to a file that points to a true repo, then to which one it is
> relative?

Despite the fact that I doubt the usefulness of an .git file at
all, it IMHO should be interpreted as an kind of userland symlink.


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@xxxxxxxx
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]