* Fwd: git status bug problem. [not found] <970bc7c80806230619i6c060c4eld329729ec7eef1da@mail.gmail.com> @ 2008-06-23 13:22 ` Ben Bennett 2008-06-23 13:47 ` Jakub Narebski 0 siblings, 1 reply; 5+ messages in thread From: Ben Bennett @ 2008-06-23 13:22 UTC (permalink / raw) To: git 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. Thanks, Ben ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: git status bug problem. 2008-06-23 13:22 ` Fwd: git status bug problem Ben Bennett @ 2008-06-23 13:47 ` Jakub Narebski 2008-06-24 1:37 ` Ben Bennett 0 siblings, 1 reply; 5+ messages in thread From: Jakub Narebski @ 2008-06-23 13:47 UTC (permalink / raw) To: Ben Bennett; +Cc: git "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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git status bug problem. 2008-06-23 13:47 ` Jakub Narebski @ 2008-06-24 1:37 ` Ben Bennett 2008-06-24 1:49 ` Mikael Magnusson 0 siblings, 1 reply; 5+ messages in thread From: Ben Bennett @ 2008-06-24 1:37 UTC (permalink / raw) To: git 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 > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git status bug problem. 2008-06-24 1:37 ` Ben Bennett @ 2008-06-24 1:49 ` Mikael Magnusson 2008-06-24 2:09 ` Ben Bennett 0 siblings, 1 reply; 5+ messages in thread From: Mikael Magnusson @ 2008-06-24 1:49 UTC (permalink / raw) To: Ben Bennett; +Cc: git 2008/6/24 Ben Bennett <benbennett@gmail.com>: > 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 The file isn't by chance matched by a git ignore rule somewhere? An easy way to check is to try and git add the file, it will say you have to use -f if it does. -- Mikael Magnusson ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git status bug problem. 2008-06-24 1:49 ` Mikael Magnusson @ 2008-06-24 2:09 ` Ben Bennett 0 siblings, 0 replies; 5+ messages in thread From: Ben Bennett @ 2008-06-24 2:09 UTC (permalink / raw) To: git Nope, it was an blank test repo . Did git init git add * (which added a few text files) did git commit -m "just a test" Modified the file , did git status and I get nothing . git-gui displays nothing . I think I hosed up something , either some dynamic lib or something. doing git status * gives me the files. On Mon, Jun 23, 2008 at 8:49 PM, Mikael Magnusson <mikachu@gmail.com> wrote: > 2008/6/24 Ben Bennett <benbennett@gmail.com>: >> 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 > > The file isn't by chance matched by a git ignore rule somewhere? An easy > way to check is to try and git add the file, it will say you have to use > -f if it does. > > -- > Mikael Magnusson > ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-06-24 2:10 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <970bc7c80806230619i6c060c4eld329729ec7eef1da@mail.gmail.com>
2008-06-23 13:22 ` Fwd: git status bug problem Ben Bennett
2008-06-23 13:47 ` Jakub Narebski
2008-06-24 1:37 ` Ben Bennett
2008-06-24 1:49 ` Mikael Magnusson
2008-06-24 2:09 ` Ben Bennett
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 NNTP newsgroup(s).