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

[FEATURE] git-gui: Staging path(s) should re-select a new path in "Unstaged Changes"

From
Birger Skogeng Pedersen <birgersp@gmail.com>
Date
Feb 28, 2018, 12:59 UTC
Message-ID
<CAGr--=Jgk==eQ4H8hiOU5x_P53gugXStORkFfTH6iPUrm43VRQ@mail.gmail.com>

When a path is selected in "Unstaged Changes", it can be staged (obviously). When it is staged, the path goes to the "Staged Changes" list, and no (new) path is selected. I propose that this action should re-select a new path, from the list of paths in "Unstaged Changes".

Steps to reproduce (in git-gui):
1. Open git-gui in a repository which has two or more uncommited, changed files.
2. Select a path in the list of "Unstaged Changes"
3. Click CTRL/CMD+T to stage the file.
4. Observe how no (new) path is selected, forcing you to re-select
another path if you want to stage it.
Message 1 of 1 in “[FEATURE] git-gui: Staging path(s) should re-select a new path in "Unstaged Changes"”
  1. Birger Skogeng PedersenFeb 28, 2018

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.