All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sergio Callegari <scallegari@arces.unibo.it>
Cc: git@vger.kernel.org
Subject: Re: git-gui shows untracked files as "changed but not updated"
Date: Wed, 14 Feb 2007 14:33:26 -0500	[thread overview]
Message-ID: <20070214193326.GB28290@spearce.org> (raw)
In-Reply-To: <45D339CD.4040603@arces.unibo.it>

Sergio Callegari <scallegari@arces.unibo.it> wrote:
> A short mail just to check if this is the intended behaviour...

Yes.  But it may not make sense.  As you may have thought, and why
this email started...

Basically it was laziness.  Originally git-gui used the current
layout (2 file lists) but the meaning of the lists was "existing
files" and "untracked files".  This turned out to really be hard to
use, especially when you are trying to work through merge conflicts.
Even _I_ had a tough time making use of that UI, and I knew what
I was doing.  ;-)

Refactoring the UI to its current design made a lot of sense, and
made git-gui very useful during merges.  But it left the untracked
files out in the wind with no place to show them.  Adding a new
file list was too much screen space (in my mind) and putting them
in the left ("Changes To Be Committed") is way wrong (as they won't
be committed by default), so the right list it was.

-- 
Shawn.

      reply	other threads:[~2007-02-14 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 16:33 git-gui shows untracked files as "changed but not updated" Sergio Callegari
2007-02-14 19:33 ` Shawn O. Pearce [this message]

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=20070214193326.GB28290@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=scallegari@arces.unibo.it \
    /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.