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

[PATCH 0/3] commit -a -m: allow the top-level tree to become empty again

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Jun 29, 2023, 13:23 UTC
Message-ID
<pull.1554.git.1688044991.gitgitgadget@gmail.com>

This patch series is in response to the bug report in https://github.com/git-for-windows/git/issues/4462 that demonstrates that git commit -a -m <msg> would no longer always stage all updates to tracked files. The bug has been introduced in Git v2.40.0.

Johannes Schindelin (3):
  do_read_index(): always mark index as initialized unless erroring out
  split-index: accept that a base index can be empty
  commit -a -m: allow the top-level tree to become empty again
 builtin/commit.c      |  7 ++-----
 read-cache.c          | 15 +++++++++------
 t/t2200-add-update.sh | 11 +++++++++++
 3 files changed, 22 insertions(+), 11 deletions(-)
base-commit: a9e066fa63149291a55f383cfa113d8bdbdaa6b3
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1554%2Fdscho%2Ffix-git-commit-a-m-when-tree-becomes-empty-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1554/dscho/fix-git-commit-a-m-when-tree-becomes-empty-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1554
-- 
gitgitgadget
Next: Johannes Schindelin via GitGitGadget
Message 1 of 6 in “commit -a -m: allow the top-level tree to become empty again”
  1. 0/3 commit -a -m: allow the top-level tree to become empty againJohannes Schindelin via GitGitGadget, Jun 29, 2023
  2. 1/3 do_read_index(): always mark index as initialized unless erroring outJohannes Schindelin via GitGitGadget, Jun 29, 2023
  3. 2/3 split-index: accept that a base index can be emptyJohannes Schindelin via GitGitGadget, Jun 29, 2023
  4. Junio C HamanoJun 29, 2023
  5. 3/3 commit -a -m: allow the top-level tree to become empty againJohannes Schindelin via GitGitGadget, Jun 29, 2023
  6. Junio C HamanoJun 29, 2023

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.