From: Ben Bennett <benbennett@gmail.com>
Date: Tue, 24 Jun 2008 01:37:15 GMT
Subject: Re: git status bug problem.
Message-ID: <970bc7c80806231837j19458b80x81063745a2ef40c4@mail.gmail.com>
In-Reply-To: <m3r6aol0u8.fsf@localhost.localdomain>

I made the initial commit.  git-gui doesn't return anything either.
Something tells me it isn't getting the cwd. Add git status *  it will
work correctly , but git-gui doesn't give anything.

somewhere@something:~/git_test$ git status
# On branch master
nothing to commit (working directory clean)

somewhere@something:~/git_test$ git status *
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#	modified:   test/test2.txt
#
Thanks,
Ben
On Mon, Jun 23, 2008 at 8:47 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> "Ben Bennett" <benbennett@gmail.com> writes:
>
>> I can't seem to get git status to return that a file has changed. I
>> think my environment is hosed up, but I don't know for sure. My
>> machine is ubuntu 8.04  with kernel  2.6.24-17-generic #1 SMPx86_64
>> GNU/Linux . I set up a test repo and it added one file to it ,
>> modified the file and saved . Doing git status returns nothing, git
>> gui finds no modified files. Doing git add * finds the modified file
>> and stages it. I can get someone a strace for the git status it is
>> only about a 1 page.
>
> You should have got something like the following:
>
> # On branch master
> # Changes to be committed:
> #   (use "git reset HEAD <file>..." to unstage)
> #
> #       new file:   bar
> #
> # Changed but not updated:
> #   (use "git add <file>..." to update what will be committed)
> #
> #       modified:   bar
> #
>
> BTW. you have made initial commit, did you?
>
> --
> Jakub Narebski
> Poland
> ShadeHawk on #git
>