From: Carlo Arenas <carenas@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Xingman Chen <xichixingman@gmail.com>
Subject: Re: [PATCH] apply: keep buffer/size pair in sync when parsing binary hunks
Date: Mon, 9 Aug 2021 22:26:51 -0700 [thread overview]
Message-ID: <CAPUEsphWN_-BWyfF9mnPhL56RSnmPZfmvh_QwhjoAb3xin8V-w@mail.gmail.com> (raw)
In-Reply-To: <YRHQAFDXs5xvyDND@coredump.intra.peff.net>
On Mon, Aug 9, 2021 at 9:24 PM Jeff King <peff@peff.net> wrote:
> diff --git a/apply.c b/apply.c
> index 44bc31d6eb..4ed4b27169 100644
> --- a/apply.c
> +++ b/apply.c
> @@ -1917,6 +1917,7 @@ static struct fragment *parse_binary_hunk(struct apply_state *state,
>
> state->linenr++;
> buffer += llen;
> + size -= llen;
> while (1) {
Ironically, I was looking at this code because of your previous
patch[1] that you suggested was ugly
and because I was going to suggest moving from a for to a while loop
to avoid the overly long line.
It is interesting to note though, that having a for (and obviously
removing the last 2 lines from the loop) with a comma separated
increment instead would
have made this issue IMHO more obvious, and also why I decided against
that; would it be a good idea to fix that as well?
for (; ; buffer += llen, size -= llen) {
Carlo
[1] https://lore.kernel.org/git/YRGwjgAIyLPb7g50@coredump.intra.peff.net/
next prev parent reply other threads:[~2021-08-10 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 1:01 [PATCH] apply: keep buffer/size pair in sync when parsing binary hunks Jeff King
2021-08-10 5:26 ` Carlo Arenas [this message]
2021-08-10 18:53 ` Jeff King
2021-08-12 20:56 ` Felipe Contreras
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=CAPUEsphWN_-BWyfF9mnPhL56RSnmPZfmvh_QwhjoAb3xin8V-w@mail.gmail.com \
--to=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=xichixingman@gmail.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;
as well as URLs for NNTP newsgroup(s).