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

Re: [PATCH 2/2] repack -ad: prune the list of shallow commits

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2018, 16:25 UTC
Message-ID
<xmqqh8kxrfrf.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180716173636.GA18636@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 5 quoted lines
> I'm OK with having a partial fix, or one that fixes immediate pain
> without doing a big cleanup, as long as it doesn't make anything _worse_
> in a user-visible way. And that's really my question: is pruning here
> going to bite people unexpectedly (not rhetorical -- I really don't
> know)?

Yeah, that matches the general guideline I follow when reviewing a patch that claims to make existing things better. And I do not think I can explain to a third person why pruning here is a good idea and won't cause problems, after seeing these patches and the discussion from the sideline.

> Right, I think "git gc" is absolutely the place to do such cleanups. My
> only complaint was that having it as part of repack may be unexpected.
Previous: Jeff KingNext: Johannes Schindelin
Message 7 of 47 in “repack -ad: fix after `fetch --prune` in a shallow repository”
  1. 0/2 repack -ad: fix after `fetch --prune` in a shallow repositoryJohannes Schindelin via GitGitGadget, Jul 13, 2018
  2. 1/2 repack: point out a bug handling stale shallow infoJohannes Schindelin via GitGitGadget, Jul 11, 2018
  3. 2/2 repack -ad: prune the list of shallow commitsJohannes Schindelin via GitGitGadget, Jul 11, 2018
  4. Jeff KingJul 13, 2018
  5. Johannes SchindelinJul 14, 2018
  6. Jeff KingJul 16, 2018
  7. Junio C HamanoJul 17, 2018
  8. Johannes SchindelinJul 19, 2018
  9. Junio C HamanoJul 19, 2018
  10. Junio C HamanoJul 20, 2018
  11. Jeff KingJul 20, 2018
  12. Duy NguyenJul 17, 2018
  13. Jeff KingJul 17, 2018
  14. Duy NguyenJul 18, 2018
  15. Jeff KingJul 18, 2018
  16. Duy NguyenJul 18, 2018
  17. Duy NguyenJul 17, 2018
  18. Duy NguyenJul 17, 2018
  19. Johannes SchindelinJul 19, 2018
  20. 0/2 repack -ad: fix after `fetch --prune` in a shallow repositoryJohannes Schindelin via GitGitGadget, Jul 17, 2018
  21. 1/2 repack: point out a bug handling stale shallow infoJohannes Schindelin via GitGitGadget, Jul 17, 2018
  22. 2/2 repack -ad: prune the list of shallow commitsJohannes Schindelin via GitGitGadget, Jul 17, 2018
  23. Eric SunshineJul 17, 2018
  24. Jeff KingJul 17, 2018
  25. Jeff KingJul 17, 2018
  26. Johannes SchindelinJul 19, 2018
  27. 0/3 repack -ad: fix after fetch --prune in a shallow repositoryJohannes Schindelin via GitGitGadget, Oct 22, 2018
  28. 1/3 repack: point out a bug handling stale shallow infoJohannes Schindelin via GitGitGadget, Oct 22, 2018
  29. Junio C HamanoOct 24, 2018
  30. Johannes SchindelinOct 24, 2018
  31. Johannes SchindelinOct 24, 2018
  32. 2/3 shallow: offer to prune only non-existing entriesJohannes Schindelin via GitGitGadget, Oct 22, 2018
  33. Junio C HamanoOct 24, 2018
  34. Johannes SchindelinOct 24, 2018
  35. Johannes SchindelinOct 24, 2018
  36. Jonathan TanOct 25, 2018
  37. Johannes SchindelinOct 26, 2018
  38. Jonathan TanOct 26, 2018
  39. Johannes SchindelinOct 29, 2018
  40. 3/3 repack -ad: prune the list of shallow commitsJohannes Schindelin via GitGitGadget, Oct 22, 2018
  41. Junio C HamanoOct 24, 2018
  42. Johannes SchindelinOct 24, 2018
  43. Johannes SchindelinOct 23, 2018
  44. 0/3 repack -ad: fix after fetch --prune in a shallow repositoryJohannes Schindelin via GitGitGadget, Oct 24, 2018
  45. 1/3 repack: point out a bug handling stale shallow infoJohannes Schindelin via GitGitGadget, Oct 24, 2018
  46. 3/3 repack -ad: prune the list of shallow commitsJohannes Schindelin via GitGitGadget, Oct 24, 2018
  47. 2/3 shallow: offer to prune only non-existing entriesJohannes Schindelin via GitGitGadget, Oct 24, 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.