From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: nik.borisov@suse.com, konstantin@linuxfoundation.org,
tools@kernel.org, tools@linux.kernel.org
Subject: Re: b4 diff failure scenario
Date: Tue, 13 Feb 2024 16:35:29 +0000 (UTC) [thread overview]
Message-ID: <20240213-b218425c2-4f45ba76151b@bugzilla.kernel.org> (raw)
In-Reply-To: <b93b0a56-0207-4538-9413-36d59c20ca2e@suse.com>
Konstantin Ryabitsev writes in commit bc83b76296315abd62fdfcec2276d96e3b611f7a:
diff: make the algorithm more forgiving
Be more forgiving when preparing fake-am ranges, so that series that
apply cleanly without a perfect hash object matches are still possible
to diff.
Reported-by: Nikolay Borisov <nik.borisov@suse.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218425
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
(via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=bc83b7629631)
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
prev parent reply other threads:[~2024-02-13 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 8:51 b4 diff failure scenario Nikolay Borisov
2024-01-26 16:32 ` Konstantin Ryabitsev
2024-01-26 16:35 ` Kernel.org Bugbot
2024-02-13 16:35 ` Kernel.org Bugbot [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=20240213-b218425c2-4f45ba76151b@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=nik.borisov@suse.com \
--cc=tools@kernel.org \
--cc=tools@linux.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).