From: Gustavo Padovan <gus@collabora.com>
To: "helpdesk" <helpdesk@kernel.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"kernelci lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: kernel.org email account for KernelCI
Date: Thu, 10 Jul 2025 12:47:53 -0300 [thread overview]
Message-ID: <197f5059619.67381650261123.8906384152523459318@collabora.com> (raw)
In-Reply-To: <197f4fc4468.7d520309253626.7085799435648700480@collabora.com>
---- On Thu, 10 Jul 2025 12:37:42 -0300 Gustavo Padovan <gus@collabora.com> wrote ---
> Hello,
>
> At KernelCI we are currently struggling with the Gmail API and plain-text.
> Our recipients keep getting emails with line wraps and we can't figure out
> why. Both myself and AI dived into it and no luck so far. End of the day
> Gmail is really for HTML based emails.
>
> We received a feedback from the linux-next folks[2] that the fact that
> log excerpts shared in the regression report has line wraps makes it
> harder for them to read it. (examples [2}).
>
> Would it be possible to setup ci@kernel.org or kernelci@kernel.org for
> KernelCI to send its reports from there? That could be a great solution
> to our problem if you can serve emails for us.
I was just informed that linux.dev is an option too. And the process
is through helpdesk, so leaving this here for you evaluation and answer.
>
> Best,
>
> - Gus
>
> [1] https://lore.kernel.org/kernelci/197e685ded3.e673ce7447423.785163730221310361@collabora.com/T/#t
> [2] https://groups.io/g/kernelci-results/message/58934
>
>
> --
> Gustavo Padovan
>
> Collabora Ltd.
>
>
next prev parent reply other threads:[~2025-07-10 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 15:37 kernel.org email account for KernelCI Gustavo Padovan
2025-07-10 15:47 ` Gustavo Padovan [this message]
[not found] ` <CAKkv+gwwWNUq5skPg81nH50axGVYqf8Gg0snCmEb9SMNexn_xQ@mail.gmail.com>
2025-07-11 13:14 ` Gustavo Padovan
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=197f5059619.67381650261123.8906384152523459318@collabora.com \
--to=gus@collabora.com \
--cc=helpdesk@kernel.org \
--cc=kernelci@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
/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).