From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, Sam Bostock <sam.bostock@shopify.com>
Subject: Re: What's cooking in git.git (Jan 2026, #10)
Date: Thu, 29 Jan 2026 21:43:52 -0800 [thread overview]
Message-ID: <xmqqo6mb8xk7.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cSH3exmnXXarrGb+UU4izOt8bJJNkEwmU+wJFGXVC8XJg@mail.gmail.com> (Eric Sunshine's message of "Thu, 29 Jan 2026 19:33:07 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Thu, Jan 29, 2026 at 6:52 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * sb/doc-worktree-prune-expire-improvement (2026-01-27) 1 commit
>> - worktree: clarify that --expire only affects missing worktrees
>>
>> The help text and the documentation for the "--expire" option of
>> "git worktree [list|prune]" have been improved.
>>
>> Will merge to 'next'?
>> source: <pull.2135.v3.git.git.1769578785381.gitgitgadget@gmail.com>
>
> Yes, I believe that the recently-posted v3 addresses all the points
> covered by the two reviewers (Eric & Junio) who commented on the
> submission.
Yup, the latest round looked good. Thanks, both of you.
next prev parent reply other threads:[~2026-01-30 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 23:52 What's cooking in git.git (Jan 2026, #10) Junio C Hamano
2026-01-30 0:33 ` Eric Sunshine
2026-01-30 5:43 ` Junio C Hamano [this message]
2026-01-30 12:06 ` Karthik Nayak
2026-01-30 14:24 ` Pushkar Singh
2026-01-30 16:50 ` Junio C Hamano
2026-01-31 13:31 ` Jean-Noël AVILA
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=xmqqo6mb8xk7.fsf@gitster.g \
--to=gitster@pobox.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