git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git status bug problem.

From
BBBen Bennett <benbennett@gmail.com>
Date
Jun 24, 2008, 01:37 UTC
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:

Show 32 quoted lines
> "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
>
Previous: Jakub NarebskiNext: Mikael Magnusson
Message 3 of 5 in “Fwd: git status bug problem.”
  1. Ben BennettJun 23, 2008
  2. Jakub NarebskiJun 23, 2008
  3. Ben BennettJun 24, 2008
  4. Mikael MagnussonJun 24, 2008
  5. Ben BennettJun 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.