From: Bill Winspur <bwinspur@gmail.com>
To: git@vger.kernel.org
Subject: git-gui disagrees with git status
Date: Mon, 10 May 2010 15:32:09 -0600 [thread overview]
Message-ID: <y2m3b1db1e51005101432je9e75a53vbb3781fa33aa83e7@mail.gmail.com> (raw)
Using git version 1.6.0.4
- Created an eclipse wkspace, with a couple of projects in it.
- Created a git repos at the workspace route, using cli.
- Using cli added the two projects to git - at this point git status
shows the following
=====
bwinspur@elm:~/ca.wydv.
workspaces/008-leaning-group/git-lrng-wksp$ git status
# On branch master
#
# Initial commit
#
# Changes to be committed:
# (use "git rm --cached <file>..." to unstage)
#
# new file: git.trial.help.bundle/.classpath
=== omitted details from this post ==
# new file: git.trial.ui.bundle/.classpath
=== omitted details from this post ==
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# .metadata/
bwinspur@elm:~/ca.wydv.workspaces/008-leaning-group/git-lrng-wksp$
=====
which is what I expected: my project folders are tracked, and
.metadata/ is untracked.
- now I bring up git gui and it shows all the files under .metadata/ as
unstaged changes, which conflicts with git status, and may be due to a
git-gui bug
Regards,
Bill Winspur
next reply other threads:[~2010-05-10 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 21:32 Bill Winspur [this message]
2010-05-10 21:39 ` git-gui disagrees with git status Shawn O. Pearce
2010-05-11 5:41 ` Miles Bader
2010-05-11 5:57 ` Johannes Sixt
2010-05-11 6:27 ` Miles Bader
2010-05-11 6:27 ` Jonathan Nieder
[not found] ` <AANLkTimcB8Ozqhti66cYzNMkIcIDIxChCj_8GDrhC4ep@mail.gmail.com>
[not found] ` <20100511140458.GA3132@progeny.tock>
[not found] ` <AANLkTilDmQBIq2xJCx_t5Qt15xXFK_3JRoiI6Y_Y8F-2@mail.gmail.com>
2010-05-11 14:27 ` Jonathan Nieder
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=y2m3b1db1e51005101432je9e75a53vbb3781fa33aa83e7@mail.gmail.com \
--to=bwinspur@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).