From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Ingo Molnar <mingo@kernel.org>,
David Miller <davem@davemloft.net>,
tj@kernel.org, akpm@linuxfoundation.org, srostedt@redhat.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4
Date: Tue, 15 Oct 2013 10:23:16 +0200 [thread overview]
Message-ID: <20131015082316.GA10651@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <00000141b8591950-3f399b8b-fdc7-41a0-b84c-bb632e8adba7-000000@email.amazonses.com>
On Mon, Oct 14, 2013 at 07:02:29PM +0000, Christoph Lameter wrote:
> On Mon, 14 Oct 2013, Peter Zijlstra wrote:
>
> > > Most kernel developers tend to use 'git send-email' to send patches to
> > > lkml, and that method is working pretty reliably.
> >
> > I always use quilt mail, it typically adds a reference to the 0/0 email
> > and ensures the time of each msg is one second ahead of the previous one
> > to ensure order is correct.
>
> Yes that I also what I expected to happen and what always happened in the
> past.
>
> > I've no idea how Christoph managed to wreck this, but normally quilt
> > mail DTRT (as opposed to git send-email which used to default to
> > endlessly deep threads -- got fixed in 1.6 or 1.7 or thereabouts).
>
> Well this is going through Amazon cloud email which may be wrecking
> things. Had a number of issues already with messages being delayed etc. I
> can try to revert to my home setup and see if that fixes things.
So your 0/x has:
Message-ID: <00000141a8a7ea27-4ab5f822-e15f-4789-a5cf-f313c402a901-000000@email.amazonses.com>
Date: Fri, 11 Oct 2013 17:54:38 +0000
1/x has:
Message-Id: <00000141a8a7eb8a-370733b2-d230-4567-96e1-74c028998bff-000000@email.amazonses.com>
References: <20131011175518.634285474@linux.com>
Date: Fri, 11 Oct 2013 17:54:39 +0000
2/x has:
Message-Id: <00000141a8a7ecfe-16f29a32-36eb-4588-a87e-6ba8e0b3a91c-000000@email.amazonses.com>
References: <20131011175518.634285474@linux.com>
Date: Fri, 11 Oct 2013 17:54:39 +0000
3/x has:
Message-Id: <00000141a8a7fa10-998dfc65-4d07-4d83-999e-31cb0056cfb3-000000@email.amazonses.com>
References: <20131011175518.634285474@linux.com>
Date: Fri, 11 Oct 2013 17:54:42 +0000
So yes, Amazon is fucking with your email, not only the msgids
(obviously) but also the date stamps are not what quilt generates.
If someone from Amazon is reading this; please comment.
next prev parent reply other threads:[~2013-10-15 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 17:54 [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4 Christoph Lameter
2013-10-11 18:08 ` David Miller
2013-10-12 16:51 ` Ingo Molnar
2013-10-14 10:32 ` Peter Zijlstra
2013-10-14 19:02 ` Christoph Lameter
2013-10-15 8:23 ` Peter Zijlstra [this message]
2013-10-14 22:24 ` Christoph Lameter
2013-10-15 7:07 ` Ingo Molnar
2013-10-16 10:37 ` Ingo Molnar
2013-10-16 14:32 ` Christoph Lameter
2013-10-14 13:09 ` Steven Rostedt
2013-10-14 19:03 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2013-10-11 16:52 Christoph Lameter
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=20131015082316.GA10651@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@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