All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/4] mark symbols that are unnecessarily public static
Date: Tue, 3 Nov 2026 11:23:30 +0100	[thread overview]
Message-ID: <aum2IssjPCGMySLm@pks.im> (raw)
In-Reply-To: <20261030182648.GE7582@coredump.intra.peff.net>

On Fri, Oct 30, 2026 at 02:26:48PM -0400, Jeff King wrote:
> On Fri, Oct 30, 2026 at 10:39:52AM -0700, Junio C Hamano wrote:
> 
> > Over the years, refactoring various subsystems, adding new callers,
> > and rewriting them from scratch, made some symbols that started as
> > static into global, and some other symbols that started as global,
> > no longer need to be visible outside a file that use them.  Here is
> > a small patch series that turns them back into file-scope static.
> > 
> > Honestly, I suspect that [3/4] was probably better with a forward
> > declaration in the preview I sent earlier, but in the longer term,
> > readers would not care if this conversion ended up in a large code
> > movement, as they do not have to even know it.
> 
> The subject for patch 1 caught my eye, but I eyeballed the whole series
> and they all look reasonable to me. I agree that big code movement is
> sometimes annoying in a diff, but the flip side is that the resulting
> file is nicer to read and maintain.

Yup, I'm happy, as well. There's two tiny nits on the commit messages,
but nothing that'd really need a reroll.

Thanks!

Patrick

      reply	other threads:[~2026-11-03 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 17:39 [PATCH 0/4] mark symbols that are unnecessarily public static Junio C Hamano
2026-10-30 17:39 ` [PATCH 1/4] ident: remove unused author_ident_sufficiently_given() Junio C Hamano
2026-10-30 18:22   ` Jeff King
2026-11-03 10:23   ` Patrick Steinhardt
2026-11-03 19:00     ` Junio C Hamano
2026-11-04  6:41       ` Patrick Steinhardt
2026-10-30 17:39 ` [PATCH 2/4] add -i: hide init/clear_add_i_state() functions Junio C Hamano
2026-11-03 10:23   ` Patrick Steinhardt
2026-11-03 19:01     ` Junio C Hamano
2026-10-30 17:39 ` [PATCH 3/4] read-cache: hide refresh_cache_entry() Junio C Hamano
2026-10-30 18:25   ` Jeff King
2026-10-30 17:39 ` [PATCH 4/4] unpack-trees: hide verify_uptodate() Junio C Hamano
2026-10-30 18:26 ` [PATCH 0/4] mark symbols that are unnecessarily public static Jeff King
2026-11-03 10:23   ` Patrick Steinhardt [this message]

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=aum2IssjPCGMySLm@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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.