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

[PATCH 0/2] Demonstrate a critical worktree/gc bug

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 8, 2017, 12:17 UTC
Message-ID
<cover.1486556262.git.johannes.schindelin@gmx.de>
... and a half-working workaround for the auto-gc case.

This patch series really is just another attempt to prod Duy into fixing this instead of dabbling with shiny new toys ;-)

Changes since "v0":
- split out the test case, both to make it easier for Duy to integrate
  it into the patch series that fixes the bug, as well as to provide a
  little more, very gentle pressure to demonstrate the severity of this
  problem.
Johannes Schindelin (2):
  worktree: demonstrate data lost to auto-gc
  worktree: demonstrate a half-working workaround for auto-gc
 t/t6500-gc.sh | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
base-commit: 6e3a7b3398559305c7a239a42e447c21a8f39ff8
Published-As: https://github.com/dscho/git/releases/tag/gc-worktree-v1
Fetch-It-Via: git fetch https://github.com/dscho/git gc-worktree-v1
-- 
2.11.1.windows.1
Next: Johannes Schindelin
Message 1 of 4 in “Demonstrate a critical worktree/gc bug”
  1. 0/2 Demonstrate a critical worktree/gc bugJohannes Schindelin, Feb 8, 2017
  2. 1/2 worktree: demonstrate data lost to auto-gcJohannes Schindelin, Feb 8, 2017
  3. 2/2 worktree: demonstrate a half-working workaround for auto-gcJohannes Schindelin, Feb 8, 2017
  4. Duy NguyenFeb 8, 2017

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.