From: Lucas De Marchi <lucas.demarchi@intel.com>
To: <tools@linux.kernel.org>, <lkp@intel.com>
Subject: trailers update and bots
Date: Fri, 16 Sep 2022 09:18:35 -0700 [thread overview]
Message-ID: <20220916161835.mpi5oyeka3b4ellx@ldmartin-desk2.lan> (raw)
It looks like there is an incompatibility with b4's updating the
trailers and bots sending "found a bug in your patch, if you fix please
include Reported-by: ..."
Example: https://lore.kernel.org/all/202209160835.MMBeObmU-lkp@intel.com/
Now if I update the trailers, it will look like the patch itself was
done because it was reported by kernel test robot, which is not true:
there was something wrong in patch that needed an update.
Should lkp (and bots in general) escape the line "Reported-by: " that
looks like a trailer, or should/could b4 deal with it in a better way?
Lucas De Marchi
next reply other threads:[~2022-09-16 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 16:18 Lucas De Marchi [this message]
2022-09-16 16:24 ` trailers update and bots Konstantin Ryabitsev
2022-09-16 16:31 ` Lucas De Marchi
2022-09-16 16:59 ` Konstantin Ryabitsev
2024-02-02 13:33 ` Lucas De Marchi
2024-02-05 17:09 ` Konstantin Ryabitsev
2024-02-05 17:15 ` Kernel.org Bugbot
2024-02-08 18:25 ` Kernel.org Bugbot
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=20220916161835.mpi5oyeka3b4ellx@ldmartin-desk2.lan \
--to=lucas.demarchi@intel.com \
--cc=lkp@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).