From: Nick Desaulniers <ndesaulniers@google.com>
To: postmaster@vger.kernel.org
Cc: "Sedat Dilek" <sedat.dilek@gmail.com>,
"Nick Clifton" <nickc@redhat.com>,
"Fāng-ruì Sòng" <maskray@google.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Segher Boessenkool" <segher@kernel.crashing.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
clang-built-linux <clang-built-linux@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux tooling mailing list
Date: Tue, 15 Sep 2020 13:49:46 -0700 [thread overview]
Message-ID: <CAKwvOdkiSLidxNxWUxCrJ_rPogORt=aGDHTkbO=yJn0FPevbpw@mail.gmail.com> (raw)
In-Reply-To: <664e5923-d65e-0a3a-1320-8b6635146676@redhat.com>
Hello postmaster,
Any thoughts on linux-toolchains@vger.kernel.org?
On Wed, Aug 26, 2020 at 3:14 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi Guys,
>
> >>>> Would it be possible to setup:
> >>>> linux-tooling@vger.kernel.org
>
> >>> s/linux-tooling/linux-toolchains (better plural toolchains)
>
> >> FWIW FreeBSD names it "freebsd-toolchain".
> >> NetBSD names it "tech-toolchain".
> >>
> >> I'd slightly prefer the singular form.
>
> > OK with singular form.
> >
> > I was thinking of GNU and LLVM toolchain*s* - that's why the plural.
>
> Personally I prefer the plural too, but it is not a big issue.
>
> I am however delighted that it looks like this idea will go ahead.
--
Thanks,
~Nick Desaulniers
next parent reply other threads:[~2020-09-15 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKwvOdkHzbPjw71n+RVXuM6Wt6PNO6fiy+14QTzthF7MCkewwg@mail.gmail.com>
[not found] ` <CA+icZUWvEzUhCjkMYAK22pkjshKmfE4a2y_W0sPPuqRtzXOtNw@mail.gmail.com>
[not found] ` <CAFP8O3LQSS4BufLEPQKOk62T0d8HoZq0kQAU8+K4d4gpY4CPag@mail.gmail.com>
[not found] ` <CA+icZUU44tbsmGfTc-2OO42V42Z02dRSs7AZCJBnXL65vJDz-Q@mail.gmail.com>
[not found] ` <664e5923-d65e-0a3a-1320-8b6635146676@redhat.com>
2020-09-15 20:49 ` Nick Desaulniers [this message]
2020-09-30 17:25 ` linux tooling mailing list Nick Desaulniers
2020-09-30 17:37 ` Peter Zijlstra
2020-09-30 19:29 ` Nick Desaulniers
2020-09-30 22:26 ` David Miller
2020-10-02 11:33 ` Nick Clifton
2020-10-02 12:01 ` Sedat Dilek
2020-10-02 17:22 ` Segher Boessenkool
2020-10-02 17:37 ` Randy Dunlap
2020-10-05 17:50 ` Nick Desaulniers
2020-10-05 17:57 ` Sedat Dilek
2020-10-05 23:59 ` David Miller
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='CAKwvOdkiSLidxNxWUxCrJ_rPogORt=aGDHTkbO=yJn0FPevbpw@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maskray@google.com \
--cc=nickc@redhat.com \
--cc=peterz@infradead.org \
--cc=postmaster@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.