git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-gui shows untracked files as "changed but not updated"

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 14, 2007, 19:33 UTC
Message-ID
<20070214193326.GB28290@spearce.org>
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.
Previous: Sergio Callegari
Message 2 of 2 in “git-gui shows untracked files as "changed but not updated"”
  1. Sergio CallegariFeb 14, 2007
  2. Shawn O. PearceFeb 14, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.