* GIT_WORK_TREE environment variable not working
@ 2010-02-01 1:33 Ron Garret
2010-02-01 5:19 ` Jeff King
0 siblings, 1 reply; 3+ messages in thread
From: Ron Garret @ 2010-02-01 1:33 UTC (permalink / raw)
To: git
What am I doing wrong here?
[ron@mickey:~/devel/gittest]$ pwd
/Users/ron/devel/gittest
[ron@mickey:~/devel/gittest]$ git status
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# git/
nothing added to commit but untracked files present (use "git add" to
track)
[ron@mickey:~/devel/gittest]$ cd
[ron@mickey:~]$ export GIT_WORK_TREE=/Users/ron/devel/gittest
[ron@mickey:~]$ git status
fatal: Not a git repository (or any of the parent directories): .git
[ron@mickey:~]$ git status --work-tree=/Users/ron/devel/gittest
fatal: Not a git repository (or any of the parent directories): .git
[ron@mickey:~]$
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GIT_WORK_TREE environment variable not working
2010-02-01 1:33 GIT_WORK_TREE environment variable not working Ron Garret
@ 2010-02-01 5:19 ` Jeff King
2010-02-01 7:09 ` Ron Garret
0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2010-02-01 5:19 UTC (permalink / raw)
To: Ron Garret; +Cc: git
On Sun, Jan 31, 2010 at 05:33:47PM -0800, Ron Garret wrote:
> What am I doing wrong here?
>
> [ron@mickey:~/devel/gittest]$ pwd
> /Users/ron/devel/gittest
> [ron@mickey:~/devel/gittest]$ git status
> # On branch master
> # Untracked files:
> # (use "git add <file>..." to include in what will be committed)
> #
> # git/
> nothing added to commit but untracked files present (use "git add" to
> track)
> [ron@mickey:~/devel/gittest]$ cd
> [ron@mickey:~]$ export GIT_WORK_TREE=/Users/ron/devel/gittest
> [ron@mickey:~]$ git status
> fatal: Not a git repository (or any of the parent directories): .git
> [ron@mickey:~]$ git status --work-tree=/Users/ron/devel/gittest
> fatal: Not a git repository (or any of the parent directories): .git
> [ron@mickey:~]$
You haven't told git where to find the repository itself. GIT_WORK_TREE
is about saying "here are my work tree files", but it is explicitly not
about "here is where my .git directory is". That lets you keep the two
in totally separate locations. E.g., you could do something like
tracking /etc, but keep your .git directory in /var.
For your case above, you would want to also
export GIT_DIR=/Users/ron/devel/gittest/.git
though since you have a fully formed repository, I don't think there is
really any advantage over just doing:
cd /Users/ron/devel/gittest && git $whatever
though perhaps that is because this is not a real use case, but rather
just you trying to figure out the feature. :)
-Peff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GIT_WORK_TREE environment variable not working
2010-02-01 5:19 ` Jeff King
@ 2010-02-01 7:09 ` Ron Garret
0 siblings, 0 replies; 3+ messages in thread
From: Ron Garret @ 2010-02-01 7:09 UTC (permalink / raw)
To: git
In article <20100201051942.GA7761@coredump.intra.peff.net>,
Jeff King <peff@peff.net> wrote:
> On Sun, Jan 31, 2010 at 05:33:47PM -0800, Ron Garret wrote:
>
> > What am I doing wrong here?
> >
> > [ron@mickey:~/devel/gittest]$ pwd
> > /Users/ron/devel/gittest
> > [ron@mickey:~/devel/gittest]$ git status
> > # On branch master
> > # Untracked files:
> > # (use "git add <file>..." to include in what will be committed)
> > #
> > # git/
> > nothing added to commit but untracked files present (use "git add" to
> > track)
> > [ron@mickey:~/devel/gittest]$ cd
> > [ron@mickey:~]$ export GIT_WORK_TREE=/Users/ron/devel/gittest
> > [ron@mickey:~]$ git status
> > fatal: Not a git repository (or any of the parent directories): .git
> > [ron@mickey:~]$ git status --work-tree=/Users/ron/devel/gittest
> > fatal: Not a git repository (or any of the parent directories): .git
> > [ron@mickey:~]$
>
> You haven't told git where to find the repository itself. GIT_WORK_TREE
> is about saying "here are my work tree files", but it is explicitly not
> about "here is where my .git directory is". That lets you keep the two
> in totally separate locations. E.g., you could do something like
> tracking /etc, but keep your .git directory in /var.
>
> For your case above, you would want to also
>
> export GIT_DIR=/Users/ron/devel/gittest/.git
Ah. Thanks!
> though since you have a fully formed repository, I don't think there is
> really any advantage over just doing:
>
> cd /Users/ron/devel/gittest && git $whatever
>
> though perhaps that is because this is not a real use case, but rather
> just you trying to figure out the feature. :)
It's a real use case. The situation is that I'm using git as a back end
for an IDE, so I can't rely on the cwd.
rg
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-02-01 7:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-01 1:33 GIT_WORK_TREE environment variable not working Ron Garret
2010-02-01 5:19 ` Jeff King
2010-02-01 7:09 ` Ron Garret
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).