public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: "René Scharfe" <l.s.r@web.de>, git@vger.kernel.org
Subject: Re: [PATCH 11/10] cocci: remove obsolete the_repository rules
Date: Fri, 16 Jan 2026 09:28:35 -0800	[thread overview]
Message-ID: <xmqqtswl8o1o.fsf@gitster.g> (raw)
In-Reply-To: <aWoMqfTmrOU8UMhm@pks.im> (Patrick Steinhardt's message of "Fri, 16 Jan 2026 11:02:17 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> On Thu, Jan 15, 2026 at 11:01:25PM +0100, René Scharfe wrote:
>> 035c7de9e9e (cocci: apply the "revision.h" part of
>> "the_repository.pending", 2023-03-28) removed the last of the repo-less
>> functions and macros mentioned in the_repository.cocci at the time.  No
>> stragglers appeared since then.  Remove the applied rules now that they
>> have outlived their usefulness.
>> 
>> Also add a reminder to eventually remove the just added rules for
>> tree.h.
>
> All of the removals look good to me, and I verified that we indeed don't
> have these functions anymore. Thanks!
>
> Patrick

Thanks, both.  These look good to me, too.

      reply	other threads:[~2026-01-16 17:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 21:30 [PATCH 00/10] tree: stop using the_repository René Scharfe
2026-01-09 21:30 ` [PATCH 01/10] environment: move access to core.maxTreeDepth into repo settings René Scharfe
2026-01-12  9:21   ` Patrick Steinhardt
2026-01-12 19:37     ` René Scharfe
2026-01-09 21:30 ` [PATCH 02/10] tree: add repo_parse_tree*() René Scharfe
2026-01-09 21:30 ` [PATCH 03/10] add-interactive: use repo_parse_tree_indirect() René Scharfe
2026-01-09 21:30 ` [PATCH 04/10] bloom: use repo_parse_tree() René Scharfe
2026-01-09 21:30 ` [PATCH 05/10] delta-islands: " René Scharfe
2026-01-09 21:30 ` [PATCH 06/10] pack-bitmap-write: " René Scharfe
2026-01-09 21:30 ` [PATCH 07/10] path-walk: use repo_parse_tree_gently() René Scharfe
2026-01-09 21:30 ` [PATCH 08/10] tree: use repo_parse_tree() René Scharfe
2026-01-12  9:21   ` Patrick Steinhardt
2026-01-09 21:30 ` [PATCH 09/10] tree: stop using the_repository René Scharfe
2026-01-12  9:21   ` Patrick Steinhardt
2026-01-12 14:22     ` Junio C Hamano
2026-01-12 15:00       ` Patrick Steinhardt
2026-01-12 15:17         ` Junio C Hamano
2026-01-12 15:20         ` Junio C Hamano
2026-01-12 15:28           ` Patrick Steinhardt
2026-01-12 19:37             ` René Scharfe
2026-01-13  6:13               ` Patrick Steinhardt
2026-01-09 21:30 ` [PATCH 10/10] cocci: convert parse_tree functions to repo_ variants René Scharfe
2026-01-15 22:01 ` [PATCH 11/10] cocci: remove obsolete the_repository rules René Scharfe
2026-01-16 10:02   ` Patrick Steinhardt
2026-01-16 17:28     ` Junio C Hamano [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=xmqqtswl8o1o.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    --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