From: Nick Desaulniers <ndesaulniers@google.com>
To: tools@linux.kernel.org
Cc: Mark Brown <broonie@kernel.org>, Josh Poimboeuf <jpoimboe@kernel.org>
Subject: b4 am and cover letter mistakes
Date: Wed, 12 Apr 2023 12:06:00 -0700 [thread overview]
Message-ID: <CAKwvOdncRCGiUA0Au-DOS0zt8KacouWxR2K3xQLdAS3E_8YpYw@mail.gmail.com> (raw)
Hello!
A second recent issue I ran into with b4 was applying a series was
failing for me because the number of patches was being parsed from the
header, which had a typo.
https://github.com/mricon/b4/issues/2
I'm sure such cases are rare, but reporting it here in case there's
anything to be done in b4 (see something, say something, but this
isn't at all a blocker for me).
--
Thanks,
~Nick Desaulniers
reply other threads:[~2023-04-12 19:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKwvOdncRCGiUA0Au-DOS0zt8KacouWxR2K3xQLdAS3E_8YpYw@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=broonie@kernel.org \
--cc=jpoimboe@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).