* why can *some* git commands not be run from within .git directory?
@ 2017-11-14 9:18 Robert P. J. Day
2017-11-14 9:38 ` Bryan Turner
0 siblings, 1 reply; 3+ messages in thread
From: Robert P. J. Day @ 2017-11-14 9:18 UTC (permalink / raw)
To: Git Mailing list
just noticed something i was unaware of -- some git commands can't
be run if i'm in the .git directory, while others can. for example,
if i "cd .git", commands like this work just fine:
$ git show
$ git branch
$ git log
but others seem unwilling to determine the "working tree":
$ git status
fatal: This operation must be run in a work tree
$
and:
$ git stash list
fatal: /usr/libexec/git-core/git-stash cannot be used without a working tree.
$
what's the distinction between commands that can work this way, and
commands that can't?
rday
p.s. i will refrain from pointing out the inconsistency in using the
phrases "work tree" and "working tree" to mean the same thing, when
there is a distinct "worktree" entity.
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: why can *some* git commands not be run from within .git directory?
2017-11-14 9:18 why can *some* git commands not be run from within .git directory? Robert P. J. Day
@ 2017-11-14 9:38 ` Bryan Turner
2017-11-14 9:43 ` Robert P. J. Day
0 siblings, 1 reply; 3+ messages in thread
From: Bryan Turner @ 2017-11-14 9:38 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Git Mailing list
On Tue, Nov 14, 2017 at 1:18 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> just noticed something i was unaware of -- some git commands can't
> be run if i'm in the .git directory, while others can. for example,
> if i "cd .git", commands like this work just fine:
>
> $ git show
> $ git branch
> $ git log
>
> but others seem unwilling to determine the "working tree":
Once Git finds a .git directory, or determines it's in one, it doesn't
look "higher"; instead, it runs like it's in a bare clone. That means
any command that requires a work tree or an index generally won't
work. Of course, you can still tell Git where the work tree is and
then the commands work fine from the .git directory:
incom@Jael MINGW64 /c/Temp/example/.git (GIT_DIR!)
$ GIT_WORK_TREE=.. git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
>
> $ git status
> fatal: This operation must be run in a work tree
> $
>
> and:
>
> $ git stash list
> fatal: /usr/libexec/git-core/git-stash cannot be used without a working tree.
> $
>
> what's the distinction between commands that can work this way, and
> commands that can't?
>
> rday
>
> p.s. i will refrain from pointing out the inconsistency in using the
> phrases "work tree" and "working tree" to mean the same thing, when
> there is a distinct "worktree" entity.
No you won't, clearly.
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> https://urldefense.proofpoint.com/v2/url?u=http-3A__crashcourse.ca&d=DwIBAg&c=wBUwXtM9sKhff6UeHOQgvw&r=uBedA6EFFVX1HiLgmpdrBrv8bIDAScKjk1yk9LOASBM&m=yPGW_MCaDCBECSMjz40m8vsxUhljCB3dnrQ4TBi8PtE&s=-JNZXqYtyY7CIJGy65WWa88Kq7BaelyajFehPQZkvo4&e=
>
> Twitter: https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_rpjday&d=DwIBAg&c=wBUwXtM9sKhff6UeHOQgvw&r=uBedA6EFFVX1HiLgmpdrBrv8bIDAScKjk1yk9LOASBM&m=yPGW_MCaDCBECSMjz40m8vsxUhljCB3dnrQ4TBi8PtE&s=-9gIAxcdRGPmIz1rpLLb7nl14azEwoE-fOJ-IxAYi18&e=
> LinkedIn: https://urldefense.proofpoint.com/v2/url?u=http-3A__ca.linkedin.com_in_rpjday&d=DwIBAg&c=wBUwXtM9sKhff6UeHOQgvw&r=uBedA6EFFVX1HiLgmpdrBrv8bIDAScKjk1yk9LOASBM&m=yPGW_MCaDCBECSMjz40m8vsxUhljCB3dnrQ4TBi8PtE&s=prnIhreU-Vhx0V6lRCBQEPbJk2P8bPlHcRFus1X_6wM&e=
> ========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: why can *some* git commands not be run from within .git directory?
2017-11-14 9:38 ` Bryan Turner
@ 2017-11-14 9:43 ` Robert P. J. Day
0 siblings, 0 replies; 3+ messages in thread
From: Robert P. J. Day @ 2017-11-14 9:43 UTC (permalink / raw)
To: Bryan Turner; +Cc: Git Mailing list
On Tue, 14 Nov 2017, Bryan Turner wrote:
> On Tue, Nov 14, 2017 at 1:18 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > just noticed something i was unaware of -- some git commands can't
> > be run if i'm in the .git directory, while others can. for example,
> > if i "cd .git", commands like this work just fine:
> >
> > $ git show
> > $ git branch
> > $ git log
> >
> > but others seem unwilling to determine the "working tree":
>
> Once Git finds a .git directory, or determines it's in one, it
> doesn't look "higher"; instead, it runs like it's in a bare clone.
> That means any command that requires a work tree or an index
> generally won't work. Of course, you can still tell Git where the
> work tree is and then the commands work fine from the .git
> directory:
ah, thank you, that clarifies it.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-11-14 9:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-14 9:18 why can *some* git commands not be run from within .git directory? Robert P. J. Day
2017-11-14 9:38 ` Bryan Turner
2017-11-14 9:43 ` Robert P. J. Day
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).