All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Bill Winspur <bwinspur@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-gui disagrees with git status
Date: Mon, 10 May 2010 14:39:26 -0700	[thread overview]
Message-ID: <20100510213926.GA7156@spearce.org> (raw)
In-Reply-To: <y2m3b1db1e51005101432je9e75a53vbb3781fa33aa83e7@mail.gmail.com>

Bill Winspur <bwinspur@gmail.com> wrote:
> #
> # 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

Its more a feature.

git-gui shows all untracked files, recursively expanding any
directories which contain untracked files.  git status collapses
them up.  If you don't want to track a directory, maybe you should
configure it in one of the many gitignore locations so neither git
status nor git gui shows it.

-- 
Shawn.

  reply	other threads:[~2010-05-10 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 21:32 git-gui disagrees with git status Bill Winspur
2010-05-10 21:39 ` Shawn O. Pearce [this message]
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=20100510213926.GA7156@spearce.org \
    --to=spearce@spearce.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.