From: michael.casadevall@linaro.org (Michael Casadevall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2] ARM VM System Specification
Date: Tue, 01 Apr 2014 05:57:29 -0400 [thread overview]
Message-ID: <533A8D89.9000500@linaro.org> (raw)
In-Reply-To: <1396345749.8667.74.camel@kazak.uk.xensource.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/01/2014 05:49 AM, Ian Campbell wrote:
> On Mon, 2014-03-31 at 10:26 -0700, Christoffer Dall wrote:
>> However, that may be a pain to update
>
> Very much, and there would be nothing worse than having multiple
> divergent copies of the spec.
>
>> so the preferred method could be to host it in either its current
>> form (clear-text) or publish some versioned PDF somewhere and
>> simply point to it from the compliant software pieces.
>
> I think that would be best.
>
> I'm at a loss to suggest a suitable neutral home though I'm
> afraid.
>
I agree with formal PDF (or TeX/plain text) releases + versioning;
something I can print out and hit people with always works great for
spec compliance.
On the topic of hosting, if Linaro itself isn't neutral enough, what
about under the Linux Foundation? They already host a bunch of
standards like the FHS.
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTOo2JAAoJEGKVRgSEnX1Qu+gH/ja+aqOqc04gbpFvuarHtzeM
nLtJ1ie4JKOJTVqqQz+lgPhx+r3H9PrMFZnGvzs8H6GYSaU66i/SHKU150J1Ig5M
1w4DYqQj7DEClpoNmpPZVJJbevp70/wDH1wFSJZXJmxV9yOpMtrNZXwB60KANP2f
MJDF+iDLIkv8vRPYQJEmuV4PMcJQs88X91eEb67jChX1ntMiiDAFSM6t2cRyfVG0
la4Ujk/p/u+Kr43wbhQITOKXZpWCtI8gjp7wTuZc+EDIhmufd5uiQ2VyTZaMkPkV
xuX9871Y8VHGxCkAmhHPODbp3Wd4VUP2ewOYnTRYR2IIRpa4gNNLUa+MSdrL/sU=
=2ub7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-04-01 9:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:45 [RFC v2] ARM VM System Specification Christoffer Dall
2014-03-30 22:10 ` Olof Johansson
2014-03-31 17:26 ` Christoffer Dall
2014-04-01 9:49 ` Ian Campbell
2014-04-01 9:57 ` Michael Casadevall [this message]
2014-04-01 10:16 ` Grant Likely
2014-04-29 14:42 ` Christoffer Dall
2014-04-30 8:14 ` Grant Likely
2014-06-10 14:42 ` Peter Maydell
2014-06-10 15:03 ` Ian Campbell
2014-06-10 17:00 ` Paolo Bonzini
2014-06-10 17:04 ` Christopher Covington
2014-06-10 18:08 ` Peter Maydell
2014-06-10 18:56 ` Paolo Bonzini
2014-06-10 19:18 ` Paolo Bonzini
2014-06-10 19:18 ` Paolo Bonzini
2014-06-11 6:54 ` Christoffer Dall
2014-06-11 8:16 ` Paolo Bonzini
2014-06-11 9:06 ` Arnd Bergmann
2014-06-30 16:19 ` Jon Masters
2014-06-30 20:46 ` Christoffer Dall
2014-06-30 21:14 ` Peter Maydell
2014-07-01 17:03 ` Stefano Stabellini
2014-07-01 17:10 ` Peter Maydell
2014-07-02 10:13 ` Christoffer Dall
2014-06-11 11:33 ` Grant Likely
2014-06-11 11:58 ` Arnd Bergmann
2014-06-11 12:02 ` Grant Likely
2014-06-11 14:14 ` Peter Maydell
2014-06-10 16:44 ` Claudio Fontana
2014-06-10 19:21 ` Arnd Bergmann
2014-06-11 9:50 ` Stefano Stabellini
2014-06-11 9:55 ` Christoffer Dall
2014-06-11 11:28 ` Grant Likely
2014-06-11 12:04 ` Christoffer Dall
2014-06-11 10:27 ` Arnd Bergmann
2014-06-11 11:22 ` Grant Likely
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=533A8D89.9000500@linaro.org \
--to=michael.casadevall@linaro.org \
--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).