threads / discuss / 17202

Weird behaviour of git status

Subject: Weird behaviour of git status

## tl;dr

3 messages between Jan 16, 2009 and Jan 16, 2009.

replies: 2people: 3as markdown or json

Nicolas Morey-Chaisemartin· Jan 16, 2009, 08:42 UTC · lore

Hello everyone,

I just noticed a weird behaviour in git status. I have created new files in different directories in my project. I have added all of them in the index with git add. When I run "git status" It shows me that all my 3 files are in the index. However if I run git-status specifying a directory, it returns that the file in this directory are in the index but the other one isn't.

In my opinion, it should
- either display all the files as in the index (specifying a directory
wouldn't have any effect then)
- treat only file in the specified dir. So "external" files wouldn't be
shown at all.

Thanks

Nicolas

Here are the logs _________________________ moreychn@uranus-ubuntu:~/workspace/git/osmdc$ git --version git version 1.6.1 moreychn@uranus-ubuntu:~/workspace/git/osmdc/include$ git status # On branch v3 # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: devmgr_common.h # new file: devmgr_types.h # new file: ../src/devmgr_common.c # # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: ../src/osmdc_devmgr.h # moreychn@uranus-ubuntu:~/workspace/git/osmdc/include$ git status . # On branch v3 # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: devmgr_common.h # new file: devmgr_types.h # # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: ../src/osmdc_devmgr.h # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # ../src/devmgr_common.c

Wincent Colaiuta· Jan 16, 2009, 09:44 UTC · re: Nicolas Morey-Chaisemartin · lore

Re: Weird behaviour of git status

El 16/1/2009, a las 9:42, Nicolas Morey-Chaisemartin escribió:

Show 17 quoted lines

> Hello everyone,
>
> I just noticed a weird behaviour in git status.
> I have created new files in different directories in my project.
> I have added all of them in the index with git add.
> When I run "git status" It shows me that all my 3 files are in the  
> index.
> However if I run git-status specifying a directory, it returns that  
> the
> file in this directory are in the index but the other one isn't.
>
> In my opinion, it should
> - either display all the files as in the index (specifying a directory
> wouldn't have any effect then)
> - treat only file in the specified dir. So "external" files wouldn't  
> be
> shown at all.

"git status" shows you what would be committed if you ran "git commit" with the same parameters. So in your example, the output for "git status ." is exactly as you would expect.

This is stated in the man page.

Cheers, Wincent

Sverre Rabbelier· Jan 16, 2009, 13:17 UTC · re: Wincent Colaiuta · lore

Re: Weird behaviour of git status

On Fri, Jan 16, 2009 at 10:44, Wincent Colaiuta <win@wincent.com> wrote:

Show 5 quoted lines

> "git status" shows you what would be committed if you ran "git commit" with
> the same parameters. So in your example, the output for "git status ." is
> exactly as you would expect.
>
> This is stated in the man page.

This is one of the first things I stumbled on when I started using git. I often times wanted to do "git status -- pathspec" to see only what changed in a certain directory, rather than what would be committed if only the contents of that directory is committed.

-- 
Cheers,

Sverre Rabbelier