From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: users <users@linux.kernel.org>, tools@linux.kernel.org
Subject: Re: Re: b4 modifying Cc-tags
Date: Tue, 2 Jan 2024 10:01:17 -0500 [thread overview]
Message-ID: <20240102-axiomatic-gabby-whale-48d3bb@lemur> (raw)
In-Reply-To: <CAMuHMdVhyjjcyxMAGF8rAqmyqin=xjWH0fhhOjqbq7rH4f-RNw@mail.gmail.com>
On Tue, Jan 02, 2024 at 09:07:25AM +0100, Geert Uytterhoeven wrote:
> Hi Konstantin,
>
> On Tue, Jan 2, 2024 at 9:02 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Happy New Year!
> >
> > "b4 am" converts
> >
> > Cc: linux-m68k@lists.linux-m68k.org
> >
> > in the patch body to
> >
> > Cc: <linux-m68k@lists.linux-m68k.org>
> >
> > causing a warning from scripts/checkpatch.pl:
> >
> > WARNING: Use a single space after Cc:
> >
> > Reproducer:
> >
> > b4 am 2023121940-enlarged-editor-c9a8@gregkh
> > cat *mbx | formail -s scripts/checkpatch.pl
Thank you for the report -- fixed in master and backported to stable-0.12.y.
> One more legitimate message caught by the overzealous
>
> 550 5.7.1 Your message looked spammy to us. Please check
> https://subspace.kernel.org/etiquette.html and resend.
>
> Thanks for fixing!
The main problem is that your From: is @linux-m68k.org, but you send from
Gmail. I'm afraid there isn't much I can do to tweak things on our end -- even
if we make exceptions for your address on our end, your emails will still
likely be rejected or sent to spam when we try to deliver them.
This really should be fixed on the linux-m68k.org side of things.
-K
next parent reply other threads:[~2024-01-02 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMuHMdVGqTM08DvsAjZ45wn1HTR0Grh8Ewj9q21pPwJmbok5hw@mail.gmail.com>
[not found] ` <CAMuHMdVhyjjcyxMAGF8rAqmyqin=xjWH0fhhOjqbq7rH4f-RNw@mail.gmail.com>
2024-01-02 15:01 ` Konstantin Ryabitsev [this message]
[not found] ` <CAMuHMdVtCfkLCb=d59XDELJO53jXJmo03iLcCwvMq54BFiUpFA@mail.gmail.com>
2024-01-02 15:59 ` Re: Re: b4 modifying Cc-tags Konstantin Ryabitsev
2024-01-02 17:03 ` Geert Uytterhoeven
2024-01-02 17:12 ` Greg KH
2024-01-02 20:49 ` Konstantin Ryabitsev
2024-01-03 0:44 ` Pali Rohár
2024-01-03 4:35 ` Linus Torvalds
2024-01-03 5:03 ` Konstantin Ryabitsev
2024-01-03 5:25 ` Linus Torvalds
2024-01-04 0:55 ` Pali Rohár
2024-01-04 17:14 ` Luck, Tony
2024-01-03 12:26 ` Geert Uytterhoeven
2024-01-03 13:19 ` James Bottomley
2024-01-04 0:41 ` Pali Rohár
2024-01-04 9:36 ` Geert Uytterhoeven
2024-01-04 12:45 ` Uwe Kleine-König
2024-01-05 1:27 ` Pali Rohár
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=20240102-axiomatic-gabby-whale-48d3bb@lemur \
--to=konstantin@linuxfoundation.org \
--cc=geert@linux-m68k.org \
--cc=tools@linux.kernel.org \
--cc=users@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).