linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hank Leininger via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: ndesaulniers@google.com
Cc: linux-kbuild@vger.kernel.org, masahiroy@kernel.org,
	michal.lkml@markovi.net, nhuck@google.com, rdunlap@infradead.org,
	sam@ravnborg.org
Subject: [Kernel.org Helpdesk #93182] [linuxfoundation.org #93182] Re: linux-kbuild missing from lore?
Date: Wed, 8 Jul 2020 21:52:41 +0000	[thread overview]
Message-ID: <01010173306aa3a2-3ad9d9e2-4cb2-42a7-a0d5-796cdf126db0-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <20200708214526.GA1893@ultron.spinoli.org>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

On Wed, Jul 08, 2020 at 01:49:18PM -0700, Nick Desaulniers wrote:
> On Wed, Jul 8, 2020 at 1:43 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > On 7/8/20 11:42 AM, Nick Desaulniers wrote:
> > > 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?
[snip]
> > Has anyone thought about trying to get the kbuild archive from
> > marc.info/?l=linux-kbuild ?  or contacted the marc.info admin?
> 
> Clicking "add a list" on
> https://marc.info/
> opens an emailto: link to webguy@marc.info, so adding them here.
> Dear marc.info admin, is exporting a copy of the linux-kbuild mail
> archive something that you can help us with?

Hi! That sounds like it should be doable; we keep .gz backups of all
the lists we're subscribed to. At a quick glance I have them going back
to Jan 2, 2008, I thiiiink uninterrupted. There's probably some spam
that got sent to the list and/or sent to our subscribed address
included.

Can someone please contact me off-thread and we'll work out details of
how to best get them to you?

Thanks,

--

Hank Leininger <hlein@marc.info>
ED0E 3040 4240 1DD9 5B2E  6DEC A60B CB9D 0939 76F7


[-- Attachment #2: Type: application/x-rt-original-message, Size: 5345 bytes --]

  parent reply	other threads:[~2020-07-08 21:52 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
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 [this message]
     [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=01010173306aa3a2-3ad9d9e2-4cb2-42a7-a0d5-796cdf126db0-000000@us-west-2.amazonses.com \
    --to=kernel-helpdesk@rt.linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.com \
    --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).