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

Re: [RFC 00/11] Make reference pruning more configurable

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 4, 2013, 20:25 UTC
Message-ID
<xmqq1u1sl5x6.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1386135890-13954-1-git-send-email-mhagger@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 8 quoted lines
> But even though "--prune=<pattern>" is no longer needed to prevent tag
> nuking, it might be useful to somebody for other purposes, and
> therefore I am submitting it to the list as an RFC.  Maybe there is a
> use case associated with non-branch, non-tag references, like perhaps
> Gerrit pull request-related references?
>
> Personally, I am -0 on this series.  I think it adds more complication
> (code, documentation, etc) than its usefulness justifies.

I tend to agree. Even though selective "only prune these if the other side no longer have corresponding refs" sounds like a great flexibility as a concept, the user needs to know that the local refs that match given patterns cannot come from remotes other than the one that fetch is talking with, which is already too complicated for the human user to grok ;-) "Don't mix refs from different sources in a random hierarchy" is probably a good advice and when adhered to there is no need for such a selective pruning.

> So, if anybody can think of a compelling use case for this feature,
> please make your case!
Thanks.
Previous: Michael Haggerty
Message 15 of 15 in “[RFC 00/11] Make reference pruning more configurable”
  1. Michael HaggertyDec 4, 2013
  2. 01/11 get_stale_heads(): allow limiting to refname patternsMichael Haggerty, Dec 4, 2013
  3. 02/11 remote.c: add infrastructure for parsing --prune optionsMichael Haggerty, Dec 4, 2013
  4. Duy NguyenDec 4, 2013
  5. Michael HaggertyDec 4, 2013
  6. 03/11 fetch: use the new functions for handling --prune optionsMichael Haggerty, Dec 4, 2013
  7. 04/11 remote: use the new functions for handling --prune optionsMichael Haggerty, Dec 4, 2013
  8. 05/11 remote.c: add infrastructure to handle --prune=<pattern>Michael Haggerty, Dec 4, 2013
  9. 06/11 fetch --prune: allow refname patterns to be specifiedMichael Haggerty, Dec 4, 2013
  10. 07/11 remote update --prune: allow refname patterns to be specifiedMichael Haggerty, Dec 4, 2013
  11. 08/11 string_list_append_list(): new functionMichael Haggerty, Dec 4, 2013
  12. 09/11 remote prune: allow --prune=<pattern> optionsMichael Haggerty, Dec 4, 2013
  13. 10/11 remote show: allow --prune=<pattern> optionsMichael Haggerty, Dec 4, 2013
  14. 11/11 remote: allow prune patterns to be configuredMichael Haggerty, Dec 4, 2013
  15. Junio C HamanoDec 4, 2013

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.