From: Jakub Narebski <jnareb@gmail.com>
To: "Ben Bennett" <benbennett@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: git status bug problem.
Date: Mon, 23 Jun 2008 06:47:48 -0700 (PDT) [thread overview]
Message-ID: <m3r6aol0u8.fsf@localhost.localdomain> (raw)
In-Reply-To: <970bc7c80806230622x326c5cd3mbce57949255a067b@mail.gmail.com>
"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
next prev parent reply other threads:[~2008-06-23 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2008-06-24 1:37 ` Ben Bennett
2008-06-24 1:49 ` Mikael Magnusson
2008-06-24 2:09 ` Ben Bennett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r6aol0u8.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=benbennett@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).