From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Messages rejected from the list with "Message has a suspicious header"
Date: Sun, 9 Dec 2012 19:10:28 +0100 [thread overview]
Message-ID: <20121209191028.1c97738c@skate> (raw)
In-Reply-To: <20121207231415.076a3e9f@skate>
On Fri, 7 Dec 2012 23:14:15 +0100, Thomas Petazzoni wrote:
> I just sent a series of 16 patches + cover letter, and those have been
> put into moderation for the reason "Message has a suspicious header".
>
> The thing is that those patches and cover letter have all been sent
> with the standard git send-email, so there shouldn't be anything
> "suspicious" in them. Do we have details about what was suspicious?
>
> In any case, could someone moderate the e-mails so that they appear on
> the list?
Anyone?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-12-09 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 22:14 Messages rejected from the list with "Message has a suspicious header" Thomas Petazzoni
2012-12-09 18:10 ` Thomas Petazzoni [this message]
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=20121209191028.1c97738c@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).