Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 16 Jun 2021 09:33:18 -0400
Olivier Langlois <olivier@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx>

(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@xxxxxxxxx>

That's because the email you replied to had:

 Message-ID: <def5421f-a3ae-12fd-87a2-6e584f753127@xxxxxxxxx>

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



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux