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

git-gui: Using "Stage To Commit" does not always stage all selected files.

From
Peter Oberndorfer <kumbayo84@arcor.de>
Date
Jan 24, 2010, 21:05 UTC
Message-ID
<201001242205.03412.kumbayo84@arcor.de>
Hello,
Using "Stage To Commit" in git-gui does not always stage all selected files.

After startup of git-gui the first modified file is automatically selected. Selecting another file and then using "Stage to Commit" only the second file is actually staged.

It looks like the reason for this is that selected_paths is not set when a file is automatically selected after startup/refresh/scanning.

How to reproduce: echo >> userdiff.h echo >> userdiff.c git gui& -> userdiff.c is automatically selected hold Ctrl and select userdiff.h Ctrl-T -> only userdiff.h is staged, userdiff.h remains unstaged

Greetings Peter
Message 1 of 1 in “git-gui: Using "Stage To Commit" does not always stage all selected files.”
  1. Peter OberndorferJan 24, 2010

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.