Re: [FAQ?] Rationale for git's way to manage the index

From: J. Bruce Fields <bfields@fieldses.org>
Date: May 8, 2007, 12:40 UTC
Message-ID: <20070508124027.GA14366@fieldses.org>
In-Reply-To: <20070508102836.GB27119@diana.vm.bytemark.co.uk>

On Tue, May 08, 2007 at 12:28:36PM +0200, Karl Hasselström wrote:

Show 6 quoted lines

> I think it would be worth introducing git-gui as a commit tool in the
> tutorial(s) and the manual. It gives a very nice graphical
> representation of the dirty state you're going to commit, and the
> dirty state you aren't going to commit because you haven't staged it
> yet. The only drawback is that it's a lot of work to make
> documentation with screenshots ...

You could put that on a web page someplace.

For the tutorial and user manual, could git-gui be treated similar gitk, with just a one- or two- line mention here and there? I haven't used it, so don't know where it would most logically fit in....

--b.

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