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

[PATCH 0/3] git worktree prune improvements

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
Mar 3, 2018, 03:39 UTC
Message-ID
<20180303033918.15751-1-pclouds@gmail.com>

This is something we could do to improve the situation when a user manually moves a worktree and not follow the update process (we have had the first reported case [1]). Plus a bit cleanup in gc.

I think this is something we should do until we somehow make the user aware that the worktree is broken as soon as they move a worktree manually. But there's some more work to get there.

[1] http://public-inbox.org/git/%3Caa98f187-4b1a-176d-2a1b-826c995776cd@aegee.org%3E
Nguyễn Thái Ngọc Duy (3):
  gc.txt: more details about what gc does
  worktree: delete dead code
  worktree prune: improve prune logic when worktree is moved
 Documentation/git-gc.txt               | 12 ++++++++++--
 Documentation/gitrepository-layout.txt |  5 -----
 builtin/worktree.c                     | 11 +++--------
 3 files changed, 13 insertions(+), 15 deletions(-)
-- 
2.16.1.435.g8f24da2e1a
Next: Nguyễn Thái Ngọc Duy
Message 1 of 15 in “git worktree prune improvements”
  1. 0/3 git worktree prune improvementsNguyễn Thái Ngọc Duy, Mar 3, 2018
  2. 1/3 gc.txt: more details about what gc doesNguyễn Thái Ngọc Duy, Mar 3, 2018
  3. Eric SunshineMar 3, 2018
  4. 2/3 worktree: delete dead codeNguyễn Thái Ngọc Duy, Mar 3, 2018
  5. 3/3 worktree prune: improve prune logic when worktree is movedNguyễn Thái Ngọc Duy, Mar 3, 2018
  6. Eric SunshineMar 3, 2018
  7. Randall S. BeckerMar 3, 2018
  8. Duy NguyenMar 5, 2018
  9. 0/3 git worktree prune improvementsNguyễn Thái Ngọc Duy, Mar 15, 2018
  10. 1/3 gc.txt: more details about what gc doesNguyễn Thái Ngọc Duy, Mar 15, 2018
  11. 2/3 worktree: delete dead codeNguyễn Thái Ngọc Duy, Mar 15, 2018
  12. Eric SunshineMar 18, 2018
  13. 3/3 worktree prune: improve prune logic when worktree is movedNguyễn Thái Ngọc Duy, Mar 15, 2018
  14. Eric SunshineMar 18, 2018
  15. Eric SunshineMar 18, 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.