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

Re: [PATCH v2 2/2] worktree: use 'prune' instead of 'expire' in help text

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 20, 2025, 06:11 UTC
Message-ID
<xmqqms3du1he.fsf@gitster.g>
In-Reply-To
<ff4732b72a0d8c97c668167308039918362ffb9c.1766168169.git.gitgitgadget@gmail.com>
"Sam Bostock via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 10 quoted lines
> From: Sam Bostock <sam.bostock@shopify.com>
>
> Use 'prune' instead of 'expire' when describing the --expire option's
> effect on missing worktrees, since the terminology is clearer.
>
> Signed-off-by: Sam Bostock <sam@sambostock.ca>
> ---
>  Documentation/git-worktree.adoc | 2 +-
>  builtin/worktree.c              | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Does this v2 use exactly the same commit from v1 as [1/2] and add this [2/2] as if you are saying "oops, the previous one missed something we should have updated but forgot/failed to do so; here is an improvement?"

Don't. Unless the change you deliberately made as a follow-up improvement is logically separate and significant, that is.

Thanks.
Previous: Sam Bostock via GitGitGadgetNext: Junio C Hamano
Message 11 of 14 in “worktree: clarify --expire applies to missing worktrees”
  1. worktree: clarify --expire applies to missing worktreesSam Bostock via GitGitGadget, Dec 19, 2025
  2. Eric SunshineDec 19, 2025
  3. Junio C HamanoDec 20, 2025
  4. Eric SunshineDec 20, 2025
  5. Junio C HamanoDec 20, 2025
  6. Eric SunshineDec 20, 2025
  7. 0/2 worktree: clarify --expire applies to missing worktreesSam Bostock via GitGitGadget, Dec 19, 2025
  8. 1/2 worktree: clarify --expire applies to missing worktreesSam Bostock via GitGitGadget, Dec 19, 2025
  9. Junio C HamanoDec 20, 2025
  10. 2/2 worktree: use 'prune' instead of 'expire' in help textSam Bostock via GitGitGadget, Dec 19, 2025
  11. Junio C HamanoDec 20, 2025
  12. Junio C HamanoJan 21, 2026
  13. worktree: clarify that --expire only affects missing worktreesSam Bostock via GitGitGadget, Jan 28, 2026
  14. Eric SunshineJan 30, 2026

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.