> git --work-tree=/Users/tfnico. ls-files 
That's interesting.  So, I tried changing core.worktree = 
/Users/nick.(appending the extra period).  Now I get

$ git status
fatal: This operation must be run in a work tree

> By the way, not sure why you first initialize the repo as bare, and then 
> manually re-edit it to be non-bare.. Are you following some recipe we 
> should know about?

Just got sick of typing .git in an empty directory when I wanted to edit 
config or info/exclude.  Behavior is the same either way.

I'm on git version You can see what version of git you have in use 
> by running git --version
git version here

> In any case, I have my doubts on this is actually being bug, and not by 
> design. I just can't find the docs right now to explain it. 
If you still want to report it as a bug, the place to go is the git 
> developer mailing list: http://vger.kernel.org/vger-lists.html#git

Thanks for helping with this.  I'm kinda starting to lean towards it being 
a bug; the differing behavior of git status versus git ls-files seems a bit 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to