linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Nick Clifton <nickc@redhat.com>,
	Fangrui Song <maskray@google.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
	LKML <linux-kernel@vger.kernel.org>,
	postmaster@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Behan Webster <behanw@converseincode.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux tooling mailing list
Date: Mon, 5 Oct 2020 19:57:31 +0200	[thread overview]
Message-ID: <CA+icZUXZeKi5fpF1hx_-q9aT6h7RTzMLBvZWsOMdqqDV5WzeXQ@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdktSmMF3PraK25ZKxAyhxrWRXzL74=vf5wf5m+5rBOsVA@mail.gmail.com>

On Mon, Oct 5, 2020 at 7:50 PM Nick Desaulniers <ndesaulniers@google.com> wrote:
>
> On Fri, Oct 2, 2020 at 10:37 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > On 10/2/20 10:22 AM, Segher Boessenkool wrote:
> > > On Fri, Oct 02, 2020 at 02:01:13PM +0200, Sedat Dilek wrote:
> > >> On Thu, Oct 1, 2020 at 12:26 AM David Miller <davem@davemloft.net> wrote:
> > >>> From: Nick Desaulniers <ndesaulniers@google.com>
> > >>> Date: Wed, 30 Sep 2020 12:29:38 -0700
> > >>>> linux-toolchains@vger.kernel.org
> > >>>
> > >>> Created.
> > >>
> > >> I am subscribed, too.
> > >>
> > >> Will there be a(n)...?
> > >>
> > >> * archive (for example marc.info)
> > >
> > > A lore archive would be good?
> >
> > That has already been requested.
>
> Hi David,
> Thank you for setting up the mailing list.  I appreciate it.  Now that
> the lore archive has been set up
> (https://lore.kernel.org/linux-toolchains/), would you mind linking to
> it from http://vger.kernel.org/vger-lists.html under archives of
> linux-toolchains?
>

Updating MAINTAINERS file came to my mind... Dunno where ro place the
new ML info?

- Sedat -

> >
> > >
> > >> * patchwork url
> > >
> > > We do not have any repositories associated with this list, and there
> > > won't be many patches anyway, so patchwork will only be useful as a kind
> > > of mail archive.  I can ask to set one up though, if people want that?
>
> Personally, I haven't been using patchwork.  I know some maintainers
> use it to keep track of reviews of lots of patches, but other than
> that is there a major use case for patchwork I'm missing?
>
> > >
> > >
> > > Segher
> > >
> >
> >
> > --
> > ~Randy
> >
>
>
> --
> Thanks,
> ~Nick Desaulniers

  reply	other threads:[~2020-10-05 17:57 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         ` linux tooling mailing list Nick Desaulniers
2020-09-30 17:25           ` 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 [this message]
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=CA+icZUXZeKi5fpF1hx_-q9aT6h7RTzMLBvZWsOMdqqDV5WzeXQ@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=behanw@converseincode.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=maskray@google.com \
    --cc=ndesaulniers@google.com \
    --cc=nickc@redhat.com \
    --cc=peterz@infradead.org \
    --cc=postmaster@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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 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).