From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: tgamblin@baylibre.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Patchtest results for [OE-core][PATCH] patchtest: shorten test result outputs
Date: Tue, 31 Oct 2023 15:54:02 +0100 [thread overview]
Message-ID: <14d60323-c668-411c-b3dd-c6cfe059fc86@bootlin.com> (raw)
In-Reply-To: <0101018b861b3b32-256b0c3e-5bb7-40da-83f1-f6717726db5e-000000@us-west-2.amazonses.com>
Hi Trevor,
On 31.10.23 at 15:20, Trevor Gamblin wrote:
> Thank you for your submission. Patchtest identified one
> or more issues with the patch. Please see the log below for
> more information:
>
> ---
> Testing patch /home/patchtest/share/mboxes/patchtest-shorten-test-result-outputs.patch
Thanks for this very useful service!
However, could the replies have an "In-Reply-To" header so that e-mail
clients can put the reply in the same thread as the patch?
Happy to create an entry in Bugzilla if this helps.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-10-31 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:20 Patchtest results for [OE-core][PATCH] patchtest: shorten test result outputs patchtest
2023-10-31 14:54 ` Michael Opdenacker [this message]
2023-10-31 15:06 ` Trevor Gamblin
2023-11-01 2:26 ` Mittal, Anuj
2023-11-01 2:33 ` Tim Orling
2023-11-01 2:48 ` Mittal, Anuj
2023-11-01 5:31 ` Marta Rybczynska
2023-11-01 13:48 ` Steve Sakoman
2023-11-01 14:00 ` Trevor Gamblin
[not found] ` <179368C4B8E65457.29356@lists.openembedded.org>
2023-11-01 6:27 ` Marta Rybczynska
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 17:18 patchtest
2023-11-01 17:48 patchtest
2023-11-01 17:47 patchtest
2023-10-30 15:20 patchtest
2023-10-30 13:41 patchtest
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=14d60323-c668-411c-b3dd-c6cfe059fc86@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tgamblin@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.