From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Colin Hinton <colinlewishinton@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
git@vger.kernel.org
Subject: Re: [PATCH] chdir-notify.h: Removed unused param 'name'
Date: Fri, 14 Aug 2026 13:42:54 -0700 [thread overview]
Message-ID: <xmqqwltsl9gx.fsf@gitster.g> (raw)
In-Reply-To: <20260814203100.GB2575854@coredump.intra.peff.net> (Jeff King's message of "Fri, 14 Aug 2026 16:31:00 -0400")
Jeff King <peff@peff.net> writes:
> I think this makes sense. It is often helpful in cleanup patches to
> summarize the history in the commit message. And then we can be sure
> that the unused field is OK to be removed, and it is not simply a bug
> that nobody is passing in the value.
Thanks for mentioning this. I also was curious when we lost the
users of "name", as it is hard to believe that we introduced name
that nobody uses from day one.
> I think ultimately the reason is that the only user of the "name" field
> was chdir_notify_reparent(), when it produced trace output. That went
> away in 5bf546755c (chdir-notify: drop unused `chdir_notify_reparent()`,
> 2026-06-25).
OK. That is fairly recent. The reason why we used to need reparent
but we no longer do is because...?
... goes and looks ...
Ah, because the files backend of the refs subsystem started solving
the issue it used to solve with _reparent() differently in the same
series, losing the last caller of the _reparent() API.
Makes sense.
> So those other patches were preparing for that world, though I think the
> ordering is somewhat confusing (and I won't be surprised if there was
> some intermediate state where turning on tracing might have caused a
> segfault).
>
> So AFAICT the patch itself is good, but it might be nice to give some
> explanation in the commit message.
Yes, that would be very helpful.
Thanks.
next prev parent reply other threads:[~2026-08-14 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 19:38 [PATCH] chdir-notify.h: Removed unused param 'name' Colin Hinton
2026-08-14 20:31 ` Jeff King
2026-08-14 20:42 ` Junio C Hamano [this message]
2026-08-14 21:42 ` [PATCH v2] " Colin Hinton
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=xmqqwltsl9gx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=colinlewishinton@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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