From: Patrick Steinhardt <ps@pks.im>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Christian Couder <christian.couder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2025, #02; Mon, 5)
Date: Wed, 7 May 2025 10:00:21 +0200 [thread overview]
Message-ID: <aBsTFdAX4pqJU6Nn@pks.im> (raw)
In-Reply-To: <CAPig+cTnxJ+ff2jygfsuigQbSa9QMdA1dWN+Wp4xXJQRXOvwOA@mail.gmail.com>
On Tue, May 06, 2025 at 01:50:09PM -0400, Eric Sunshine wrote:
> On Tue, May 6, 2025 at 4:35 AM Christian Couder
> <christian.couder@gmail.com> wrote:
> > On Tue, May 6, 2025 at 9:04 AM Junio C Hamano <gitster@pobox.com> wrote:
> > > * ps/maintenance-missing-tasks (2025-05-05) 7 commits
> > > - builtin/maintenance: introduce "rerere-gc" task
> > > - builtin/gc: move rerere garbage collection into separate function
> > > - builtin/maintenance: introduce "worktree-prune" task
> > > - worktree: expose function to retrieve worktree names
> > > - builtin/gc: move pruning of worktrees into a separate function
> > > - builtin/gc: remove global variables where it trivial to do
> > > - builtin/gc: fix indentation of `cmd_gc()` parameters
> > >
> > > Make repository clean-up tasks "gc" can do available to "git
> > > maintenance" front-end.
> > >
> > > Will merge to 'next'.
> > > source: <20250505-pks-maintenance-missing-tasks-v4-0-141f4df906a1@pks.im>
> >
> > I am reviewing this series and it seems to me that it's possibly
> > missing a fix for a leak that Eric Sunshine had found in a previous
> > review round.
>
> In addition to the leak[1], I also have reservations[2] about the
> "worktree: expose function to retrieve worktree names" patch.
I've addressed both of these now in v5 of this patch series. Thanks!
Patrick
next prev parent reply other threads:[~2025-05-07 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 1:20 What's cooking in git.git (May 2025, #02; Mon, 5) Junio C Hamano
2025-05-06 8:34 ` Christian Couder
2025-05-06 17:50 ` Eric Sunshine
2025-05-07 8:00 ` Patrick Steinhardt [this message]
2025-05-08 18:22 ` 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=aBsTFdAX4pqJU6Nn@pks.im \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).