Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".

From: Jakub Narebski <jnareb@gmail.com>
Date: Nov 30, 2006, 21:41 UTC
Message-ID: <eknj33$q2r$1@sea.gmane.org>
In-Reply-To: <456F4E38.50001@codeweavers.com>

Robert Shearman wrote:

Show 7 quoted lines

> Having the index exposed for even simple operations means that the user 
> has to initially learn three states instead of two. The worst thing 
> about the index is that it is a limbo state. The committed content is in 
> the history and can be viewed by gitk (and other tools that the user 
> will be introduced to later) and the working tree is exactly what the 
> user sees in their editor. Having a hidden state isn't very good from an 
> HCI point of view.

Index is accessible, just like committed contents. The fact that gitk, qgit, git-gui doesn't display state of index is their limitation.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

$ 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.