linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: kernel-helpdesk@rt.linuxfoundation.org
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Nathan Huckleberry <nhuck@google.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [Kernel.org Helpdesk #93182] Re: linux-kbuild missing from lore?
Date: Thu, 6 Aug 2020 10:27:18 -0700	[thread overview]
Message-ID: <CAKwvOd=xLc1=kRRM8NBaeXqhXOTSYDg7AgLtqRth4vm7ODFA6w@mail.gmail.com> (raw)
In-Reply-To: <01010173c1e35fde-0cbf88a3-5ebe-43fa-be6b-af9c00a50864-000000@us-west-2.amazonses.com>

On Wed, Aug 5, 2020 at 8:49 PM Chris Hoy Poy via RT
<kernel-helpdesk@rt.linuxfoundation.org> wrote:
>
>
> Hi all,
>
> This should be active at
>
> https://lore.kernel.org/linux-kbuild

Looks great! Thanks for getting this stood up for us Chris, we appreciate it.

>
> I dont think we missed any, but there might have been a few slip past the gap between the archive and the subscription being active, feel free to forward a quick list of those days if necessary, and I'll pull them in too.

Comparing https://marc.info/?l=linux-kbuild, there's a small hole
between July 8-July 27/29.  I've reached out to Hank who can help get
me the archive for those dates, and I'll rerun the sanitizer and reach
out to you with a link.  Then it looks like lore.kernel.org should be
pretty complete for kbuild.
-- 
Thanks,
~Nick Desaulniers

  parent reply	other threads:[~2020-08-06 17:27 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
     [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 [this message]
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='CAKwvOd=xLc1=kRRM8NBaeXqhXOTSYDg7AgLtqRth4vm7ODFA6w@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=kernel-helpdesk@rt.linuxfoundation.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).