From: Steven Rostedt <rostedt@goodmis.org>
To: Olivier Langlois <olivier@trillion01.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Pavel Begunkov <asml.silence@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition
Date: Wed, 16 Jun 2021 09:43:21 -0400 [thread overview]
Message-ID: <20210616094321.671b82dc@gandalf.local.home> (raw)
In-Reply-To: <f3cf3dc047dcee400423f526c1fe31510c5bcf61.camel@trillion01.com>
On Wed, 16 Jun 2021 09:33:18 -0400
Olivier Langlois <olivier@trillion01.com> wrote:
> I do not get any errors but I have noticed too that my emails weren't
> accepted by the lists.
>
> They will accept replies in already existing threads but they won't let
> me create new ones. ie: accepting my patches.
How are you sending your patches? The patches that were rejected, did not
have the "Message-ID:" tag in the header. If you look at my email (and
yours that I'm replying to now) you'll see something like this:
Message-ID: <f3cf3dc047dcee400423f526c1fe31510c5bcf61.camel@trillion01.com>
(that's from the email I'm replying to).
All emails are suppose to have this tag. This is what is used to map
replies in a way that your email client can see what email is replying to
which email. Again, from your email:
In-Reply-To: <def5421f-a3ae-12fd-87a2-6e584f753127@kernel.dk>
That's because the email you replied to had:
Message-ID: <def5421f-a3ae-12fd-87a2-6e584f753127@kernel.dk>
This is also used for mail archives, as message ids are used to
differentiate emails from each other. But if the Message-ID is missing, the
archives have no idea to map it.
I'm guessing that the mailing lists also flag any email that is missing a
Message-ID as spam.
Thus, you should find out what is wrong with your client software that is
sending out the patches, and see why it's not including the Message-ID.
-- Steve
next prev parent reply other threads:[~2021-06-16 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60be7e31.1c69fb81.a8bfb.2e54SMTPIN_ADDED_MISSING@mx.google.com>
2021-06-15 9:48 ` [PATCH v2 2/3] io_uring: minor clean up in trace events definition Pavel Begunkov
2021-06-15 21:50 ` Jens Axboe
2021-06-15 23:35 ` Steven Rostedt
2021-06-16 12:49 ` Jens Axboe
2021-06-16 19:00 ` Olivier Langlois
2021-06-16 19:02 ` Jens Axboe
2021-06-16 21:30 ` Olivier Langlois
2021-06-16 21:33 ` Jens Axboe
2021-06-20 19:15 ` Olivier Langlois
2021-06-20 20:13 ` Pavel Begunkov
2021-06-16 13:33 ` Olivier Langlois
2021-06-16 13:43 ` Steven Rostedt [this message]
2021-06-16 13:53 ` Pavel Begunkov
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=20210616094321.671b82dc@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=olivier@trillion01.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 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).