From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: RISC-V ISA Dev <isa-dev@groups.riscv.org>,
Gurjeet Singh <gurjeet@singh.im>,
Atish Patra <Atish.Patra@wdc.com>,
RISC-V SW Dev <sw-dev@groups.riscv.org>,
RISC-V HW Dev <hw-dev@groups.riscv.org>,
linux-riscv@lists.infradead.org
Subject: Re: [isa-dev] UNIX-Class Platform Specification Working Group
Date: Wed, 3 Apr 2019 02:39:06 +0000 [thread overview]
Message-ID: <CAPweEDyK4vdeMR3R74GsT3hz6vJudpb5NHvsOxq5KnABjomUSg@mail.gmail.com> (raw)
In-Reply-To: <mhng-0d3fa726-2ae0-44d4-9024-9c321c466e50@palmer-si-x1c4>
On Wed, Apr 3, 2019 at 2:53 AM Palmer Dabbelt <palmer@sifive.com> wrote:
> On Tue, 02 Apr 2019 16:42:30 PDT (-0700), gurjeet@singh.im wrote:
> > Not that I'm interested in participating, but just curious as to how these
> > officially approved groups work. Is there a mailing list for this group? Is
> > it open to public? How does one request to participate in these lists? How
> > does one follow along in these conversations, that is, where are the
> > mailing list archives for this group?
>
> There is (or will soon be) an internal RISC-V foundation mailing list. You
> sign up for it via your RISC-V foundation account
so that it is perfectly clear to all who may wish (or need) to participate
(1) what are the terms and conditions under which a "RISC-V foundation
account" may be obtained
(2) are the archives of the "internal RISC-V foundation mailing list"
to be made public and transparent so that businesses who have
mandatory transparency and third party audit and accountability
requirements are not seen to be "hiding something" by participating?
l.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-04-03 2:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 16:50 UNIX-Class Platform Specification Working Group Palmer Dabbelt
2019-04-02 17:38 ` [isa-dev] " Luke Kenneth Casson Leighton
[not found] ` <CABwTF4UW8YePYr9Ad65VSvef4-Y42VEvNUs=hPWyWcyH295zCw@mail.gmail.com>
2019-04-03 0:31 ` [hw-dev] " Luke Kenneth Casson Leighton
2019-04-03 2:43 ` Palmer Dabbelt
2019-04-03 3:34 ` Luke Kenneth Casson Leighton
2019-04-03 4:13 ` Luke Kenneth Casson Leighton
2019-04-03 4:48 ` Luke Kenneth Casson Leighton
2019-04-03 1:53 ` Palmer Dabbelt
2019-04-03 2:39 ` Luke Kenneth Casson Leighton [this message]
[not found] ` <CANs6eMn4+6XGaSOGyWoD5RK2DjQo2SUUHphqmL_dwQD-Xu-omQ@mail.gmail.com>
2019-04-07 7:36 ` [isa-dev] " Christoph Hellwig
2019-04-07 15:30 ` Jim Wilson
2019-04-08 6:50 ` Atish Patra
[not found] <CAPweEDz=JB2knNXthiKVL7QC5dxNrUf_GGmmEquT0UEo9WLs_Q@mail.gmail.com>
2019-04-03 1:53 ` [isa-dev] " Palmer Dabbelt
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=CAPweEDyK4vdeMR3R74GsT3hz6vJudpb5NHvsOxq5KnABjomUSg@mail.gmail.com \
--to=lkcl@lkcl.net \
--cc=Atish.Patra@wdc.com \
--cc=gurjeet@singh.im \
--cc=hw-dev@groups.riscv.org \
--cc=isa-dev@groups.riscv.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=sw-dev@groups.riscv.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).