From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] unpack-trees: hide verify_uptodate()
Date: Fri, 30 Oct 2026 10:31:26 +0100 [thread overview]
Message-ID: <auRj7rRyg15WYiFc@pks.im> (raw)
In-Reply-To: <xmqqqzh97d2r.fsf@gitster.g>
On Wed, Oct 28, 2026 at 02:03:08PM -0700, Junio C Hamano wrote:
> 64b1abe962 (merge-recursive: fix overwriting dirty files involved in
> renames, 2018-04-19) made this function available to external callers.
>
> With the removal of the "recursive" strategy in ad45b327c0
> (merge-recursive.[ch]: thoroughly debug these, 2025-04-08), the last
Heh, this commit message confused me for a second, until I remembered
the discussion that we had around it back then.
> external caller of this function want away.
But history checks out...
> diff --git a/unpack-trees.c b/unpack-trees.c
> index 1802809ad3..3298773490 100644
> --- a/unpack-trees.c
> +++ b/unpack-trees.c
> @@ -2269,8 +2269,8 @@ static int verify_uptodate_1(const struct cache_entry *ce,
> return add_rejected_path(o, error_type, ce->name);
> }
>
> -int verify_uptodate(const struct cache_entry *ce,
> - struct unpack_trees_options *o)
> +static int verify_uptodate(const struct cache_entry *ce,
> + struct unpack_trees_options *o)
> {
> if (!o->skip_sparse_checkout &&
> (ce->ce_flags & CE_SKIP_WORKTREE) &&
> diff --git a/unpack-trees.h b/unpack-trees.h
> index 5867e26e17..638a6b076d 100644
> --- a/unpack-trees.h
> +++ b/unpack-trees.h
> @@ -123,9 +123,6 @@ enum update_sparsity_result {
> enum update_sparsity_result update_sparsity(struct unpack_trees_options *options,
> struct pattern_list *pl);
>
> -int verify_uptodate(const struct cache_entry *ce,
> - struct unpack_trees_options *o);
> -
... and the diff looks good. So assuming this compiles and links the
change is obviously correct.
Thanks!
Patrick
prev parent reply other threads:[~2026-10-30 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 21:03 [PATCH] unpack-trees: hide verify_uptodate() Junio C Hamano
2026-10-30 9:31 ` 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=auRj7rRyg15WYiFc@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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