From: "Sam Bostock via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Sam Bostock <sam.bostock@shopify.com>
Subject: [PATCH v2 0/2] worktree: clarify --expire applies to missing worktrees
Date: Fri, 19 Dec 2025 18:16:07 +0000 [thread overview]
Message-ID: <pull.2135.v2.git.git.1766168169.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2135.git.git.1766156407442.gitgitgadget@gmail.com>
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
--
gitgitgadget
next prev parent reply other threads:[~2025-12-19 18:16 UTC|newest]
Thread overview: 11+ 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 ` Sam Bostock via GitGitGadget [this message]
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
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=pull.2135.v2.git.git.1766168169.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).