From: Junio C Hamano <gitster@pobox.com>
To: "Sam Bostock via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>,
Sam Bostock <sam.bostock@shopify.com>
Subject: Re: [PATCH v2 0/2] worktree: clarify --expire applies to missing worktrees
Date: Wed, 21 Jan 2026 11:55:13 -0800 [thread overview]
Message-ID: <xmqqzf66spum.fsf@gitster.g> (raw)
In-Reply-To: <pull.2135.v2.git.git.1766168169.gitgitgadget@gmail.com> (Sam Bostock via GitGitGadget's message of "Fri, 19 Dec 2025 18:16:07 +0000")
"Sam Bostock via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Changes from v1:
>
> * Use 'prune' instead of 'expire' when describing the --expire option's
> effect on missing worktrees, since the terminology is clearer.
>
> Sam Bostock (2):
> worktree: clarify --expire applies to missing worktrees
> worktree: use 'prune' instead of 'expire' in help text
>
> Documentation/git-worktree.adoc | 2 +-
> builtin/worktree.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
>
> base-commit: c4a0c8845e2426375ad257b6c221a3a7d92ecfda
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2135%2Fsambostock%2Fexpire-missing-worktrees-v2
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2135/sambostock/expire-missing-worktrees-v2
> Pull-Request: https://github.com/git/git/pull/2135
>
> Range-diff vs v1:
>
> 1: ddd4191ecb = 1: ddd4191ecb worktree: clarify --expire applies to missing worktrees
> -: ---------- > 2: ff4732b72a worktree: use 'prune' instead of 'expire' in help text
I think we have been expecting a reroll of this topic. Any further
progress?
next prev parent reply other threads:[~2026-01-21 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 15:00 [PATCH] worktree: clarify --expire applies to missing worktrees Sam Bostock via GitGitGadget
2025-12-19 15:11 ` Eric Sunshine
2025-12-20 5:44 ` Junio C Hamano
2025-12-20 7:14 ` Eric Sunshine
2025-12-20 7:31 ` Junio C Hamano
2025-12-20 8:23 ` Eric Sunshine
2025-12-19 18:16 ` [PATCH v2 0/2] " Sam Bostock via GitGitGadget
2025-12-19 18:16 ` [PATCH v2 1/2] " Sam Bostock via GitGitGadget
2025-12-20 6:07 ` Junio C Hamano
2025-12-19 18:16 ` [PATCH v2 2/2] worktree: use 'prune' instead of 'expire' in help text Sam Bostock via GitGitGadget
2025-12-20 6:11 ` Junio C Hamano
2026-01-21 19:55 ` Junio C Hamano [this message]
2026-01-28 5:39 ` [PATCH v3] worktree: clarify that --expire only affects missing worktrees Sam Bostock via GitGitGadget
2026-01-30 0:29 ` Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzf66spum.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=sam.bostock@shopify.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.