From: kyle@kyleam.com
To: tools@linux.kernel.org
Subject: [PATCH b4 0/2] Two fixes for LoreMessage.get_body_parts()
Date: Sat, 25 Jul 2020 23:41:13 -0400 [thread overview]
Message-ID: <20200726034115.21567-1-kyle@kyleam.com> (raw)
After using 'b4 am' to grab a series from public-inbox meta [0], I
noticed that many of the commit message bodies were missing. It turns
out that this happens when a message body consists of only a single,
non-trailer paragraph.
The second patch fixes this. The first patch addresses another issue
I spotted when debugging the dropped commit messages.
[0]: https://public-inbox.org/meta/20200724055606.27332-1-e@yhbt.net
[1/2] Fix basement detection for empty commit message bodies
[2/2] Fix handling of single-paragraph commit message bodies
b4/__init__.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
base-commit: 2737ccdd3dbf58e330ace3ec658511bfbd715059
--
2.27.0
next reply other threads:[~2020-07-26 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 3:41 kyle [this message]
2020-07-26 3:41 ` [PATCH b4 1/2] Fix basement detection for empty commit message bodies Kyle Meyer
2020-07-26 3:41 ` [PATCH b4 2/2] Fix handling of single-paragraph " Kyle Meyer
2020-07-27 14:08 ` [tools] [PATCH b4 0/2] Two fixes for LoreMessage.get_body_parts() Konstantin Ryabitsev
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=20200726034115.21567-1-kyle@kyleam.com \
--to=kyle@kyleam.com \
--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 NNTP newsgroup(s).