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

Re: [PATCH] terminology tweak: prune -> path limiting

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2018, 01:36 UTC
Message-ID
<xmqqo99v5vnc.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20181206213315.64423-1-matvore@google.com>
Matthew DeVore <matvore@google.com> writes:
> In the codebase, "prune" is a highly overloaded term, and it caused me a
> lot of trouble to figure out what it meant when it was used in the
> context of path limiting. Stop using the word "prune" when we really
> mean "path limiting."

path limiting is also used for two purposes. "pruning", which is to cull the side branches that do not contribute the changes made to the paths we are interested in, and showing only the changes to the paths that match pathspec.

AFAIK, "prune" is also used to describe unreachable loose objects, but that use is fairly isolated and have little risk of being confusing too much. Are there other uses to make you consider it "highly overloaded"?

My gut feeling is that the result is not reducing "overloading" in a meaningful way, and this change is not worth the churn, but it depends on the answer to the above question.

Thanks.
Previous: Matthew DeVoreNext: Junio C Hamano
Message 2 of 6 in “terminology tweak: prune -> path limiting”
  1. terminology tweak: prune -> path limitingMatthew DeVore, Dec 6, 2018
  2. Junio C HamanoDec 9, 2018
  3. Junio C HamanoDec 9, 2018
  4. Matthew DeVoreDec 10, 2018
  5. Junio C HamanoDec 11, 2018
  6. MATTHEW DEVOREDec 11, 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.