All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Miles Bader <miles@gnu.org>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Bill Winspur <bwinspur@gmail.com>,
	git@vger.kernel.org
Subject: Re: git-gui disagrees with git status
Date: Tue, 11 May 2010 01:27:28 -0500	[thread overview]
Message-ID: <20100511062728.GA29654@progeny.tock> (raw)
In-Reply-To: <4BE8F1DB.2060205@viscovery.net>

Johannes Sixt wrote:
>> "Shawn O. Pearce" <spearce@spearce.org> writes:

>>> Its more a feature.
>>>
>>> git-gui shows all untracked files, recursively expanding any
>>> directories which contain untracked files.  git status collapses
>>> them up.
[...]
> Oh, it *is* good behavior. Otherwise, it would not be possible to stage a
> file that resides in a currently untracked directory; you would have to
> fall back to 'git add' on the command line.

I would say rather it is the best we have.  Much better would be to
display untracked directories using a tree view (like gitk’s
treeview), starting out collapsed[1].

Jonathan

[1] http://bugs.debian.org/572805

  parent reply	other threads:[~2010-05-11  6:27 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
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 [this message]
     [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=20100511062728.GA29654@progeny.tock \
    --to=jrnieder@gmail.com \
    --cc=bwinspur@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=miles@gnu.org \
    --cc=spearce@spearce.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.