public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Karthik Nayak <karthik.188@gmail.com>,
	 Collin Funk <collin.funk1@gmail.com>,
	 git@vger.kernel.org
Subject: Re: [PATCH 1/4] ref-filter: factor out refname component counting
Date: Thu, 19 Feb 2026 10:56:53 -0800	[thread overview]
Message-ID: <xmqq8qco5zpm.fsf@gitster.g> (raw)
In-Reply-To: <20260219112149.GA3529@coredump.intra.peff.net> (Jeff King's message of "Thu, 19 Feb 2026 06:21:49 -0500")

Jeff King <peff@peff.net> writes:

>> And then p moves to the right until p[i] points at the end of the
>> string.  It does count the number of slashes in 'i', but there is no
>> satisfying simple answer to this question: "what does p mean while
>> this loop runs?".
>> ...
> Which made me wonder if I am missing some corner case, and it is not
> just counting slashes. But it must be, because "i" is never incremented
> except when we see a slash.
>
> +cc Karthik, the original author, for any wisdom, but the commit is now
> almost 10 years old.
>
> Is it worth rewriting to the "slashes" form above for clarity? I was
> afraid to touch it just to shut up Coverity, but now we have two
> confused people.

Yup, I think the answer to my "what does p mean?" question is "by
itself p has *no* meaning, but (p-refname) is maintained to be the
number of non-slash bytes we scanned so far, while i is the number
of slashes."

And from that point of view, your "count slashes in the most stupid
way that even 5 year old understands" certainly does make the result
far easier to read.

Thanks.

  reply	other threads:[~2026-02-19 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14  5:15 [PATCH] ref-filter: don't declare a strdup'd variable const before writing to it Collin Funk
2026-02-15  8:57 ` [PATCH 0/4] cleaning up ref-filter lstrip/rstrip code Jeff King
2026-02-15  9:00   ` [PATCH 1/4] ref-filter: factor out refname component counting Jeff King
2026-02-17 18:07     ` Junio C Hamano
2026-02-19 11:21       ` Jeff King
2026-02-19 18:56         ` Junio C Hamano [this message]
2026-02-20  6:00           ` [PATCH] ref-filter: clarify lstrip/rstrip " Jeff King
2026-02-22 17:04         ` [PATCH 1/4] ref-filter: factor out refname " Karthik Nayak
2026-02-15  9:02   ` [PATCH 2/4] ref-filter: simplify lstrip_ref_components() memory handling Jeff King
2026-02-15  9:05   ` [PATCH 3/4] ref-filter: simplify rstrip_ref_components() " Jeff King
2026-02-15  9:07   ` [PATCH 4/4] ref-filter: avoid strrchr() in rstrip_ref_components() Jeff King
2026-02-16  7:23     ` Patrick Steinhardt
2026-02-15  9:11   ` [PATCH 0/4] cleaning up ref-filter lstrip/rstrip code Jeff King
2026-02-15 22:23   ` Collin Funk

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=xmqq8qco5zpm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=collin.funk1@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox