From: "Joseph S. Myers" <joseph@codesourcery.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] 2038 Kernel Summit Discussion Fodder
Date: Wed, 13 Aug 2014 12:05:38 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1408131204480.1607@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CALAqxLUcfaJnxdmkn6mucepNk3QaCQdcSPLRjjeKsk_OTp=uLA@mail.gmail.com>
Please include linux-api on such discussions relating to the kernel /
userspace interface. I'm likely to pay more attention to them if I
receive them through linux-api than anything only received through direct
email.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-08-13 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 0:01 John Stultz
2014-08-13 2:06 ` Ben Hutchings
2014-08-13 4:03 ` John Stultz
2014-08-13 20:06 ` Arnd Bergmann
2015-09-19 0:04 ` H. Peter Anvin
2014-08-13 12:05 ` Joseph S. Myers [this message]
2014-08-13 15:37 ` Joseph S. Myers
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=Pine.LNX.4.64.1408131204480.1607@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=john.stultz@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.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