linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	helpdesk@kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Nathan Huckleberry <nhuck@google.com>,
	Michal Marek <michal.lkml@markovi.net>
Subject: Re: linux-kbuild missing from lore?
Date: Wed, 8 Jul 2020 11:42:03 -0700	[thread overview]
Message-ID: <CAKwvOdnknZNPuucvy0Kim6xCfyUhmNKXQiERCQcoSMYdo6=6FQ@mail.gmail.com> (raw)
In-Reply-To: <f30f6849-9d94-4ba9-f875-9ab8c0700620@infradead.org>

On Mon, Mar 16, 2020 at 6:06 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 3/16/20 5:47 PM, Masahiro Yamada wrote:
> > Hi Nick,
> >
> > On Tue, Mar 17, 2020 at 8:22 AM Nick Desaulniers
> > <ndesaulniers@google.com> wrote:
> >>
> >> Hi Masahiro,
> >> I noticed that linux-kbuild@vger.kernel.org seems to be missing from
> >> https://lore.kernel.org/lists.html.  Is that intentional or
> >> accidental?
> >> --
> >> Thanks,
> >> ~Nick Desaulniers
> >
> >
> > Thanks for letting me know this.
> > I guess it is accidental.
> >
> > In fact, I do not know what to do
> > to take good care of the kbuild ML.
>
> Maybe ask Sam Ravnborg or Michal Marek if they have kbuild ML archives.
>
> or see if they are available from some other ML archive site, like
> https://www.spinics.net/lists/linux-kbuild/
>
>
> My kbuild archive has about 20,000 emails in it, beginning around the
> middle of 2011.
> I could make that available, but I don't claim that it is complete.
>
> And I'm sure that it has some duplicate emails in it [if an email is
> kbuild-related, I put the email into this "folder", no matter what
> mailing list it came from].

https://lore.kernel.org/lists.html links to
https://www.kernel.org/lore.html links to
https://korg.docs.kernel.org/lore.html
which seems to indicate that we need such an archive.

cc'ing help desk for the request.  It looks like we need to
collect+merge then sanitize mboxes.  Randy, if we could start with
your archive, I'd be happy to help drive this across the finish line.
-- 
Thanks,
~Nick Desaulniers

  parent reply	other threads:[~2020-07-08 18:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-93182@linuxfoundation>
2020-03-16 23:22 ` linux-kbuild missing from lore? Nick Desaulniers
2020-03-17  0:47   ` Masahiro Yamada
2020-03-17  1:06     ` Randy Dunlap
2020-03-17  4:32       ` Sam Ravnborg
2020-07-08 18:42       ` Nick Desaulniers [this message]
2020-07-08 20:42         ` Randy Dunlap
2020-07-08 20:43           ` [Kernel.org Helpdesk #93182] [linuxfoundation.org #93182] " rdunlap@infradead.org via RT
2020-07-08 20:49           ` Nick Desaulniers
2020-07-08 20:49             ` [Kernel.org Helpdesk #93182] [linuxfoundation.org #93182] " Nick Desaulniers via RT
2020-07-08 21:45             ` Hank Leininger
2020-07-08 21:47               ` Nick Desaulniers
2020-07-08 21:47                 ` [Kernel.org Helpdesk #93182] [linuxfoundation.org #93182] " Nick Desaulniers via RT
2020-07-08 21:52               ` Hank Leininger via RT
     [not found]         ` <rt-4.4.0-1686-1594408327-1443.93182-6-0@linuxfoundation>
2020-07-27 21:33           ` [Kernel.org Helpdesk " Chris Hoy Poy via RT
2020-07-27 22:30             ` Nick Desaulniers
2020-07-27 22:30               ` Nick Desaulniers via RT
2020-08-06  3:49         ` Chris Hoy Poy via RT
2020-08-06  8:11           ` Masahiro Yamada
2020-08-06  8:12             ` masahiroy@kernel.org via RT
2020-08-06 17:27           ` Nick Desaulniers
2020-08-06 17:27             ` Nick Desaulniers via RT

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='CAKwvOdnknZNPuucvy0Kim6xCfyUhmNKXQiERCQcoSMYdo6=6FQ@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=helpdesk@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=nhuck@google.com \
    --cc=rdunlap@infradead.org \
    --cc=sam@ravnborg.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).