From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Richard Weinberger <richard@nod.at>
Cc: anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
helpdesk <helpdesk@kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Add linux-um archives to lore.kernel.org?
Date: Thu, 13 Oct 2022 14:57:18 +0200 [thread overview]
Message-ID: <CAMuHMdU=TurB14tkAbqb9nWYvCOcr0UUScdga25h3-oWjYfzTg@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVWWbonfT7-RRV4U9UUudUobpeAGOXpO9Y0Cyuqzy=DeQ@mail.gmail.com>
Hi Richard.
> > >>> https://korg.docs.kernel.org/lore.html says pipermail archives like
> > >>> infradead has are not ideal, but I don't have any archives at all, and
> > >>> I don't know how to get even pipermail archives out of infradead.
The first step is
https://korg.docs.kernel.org/lore.html#requesting-archival-of-an-existing-list
It doesn't make much sense to start collecting archives if the lore
collector hasn't been activated yet.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-10-13 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 19:11 Add linux-um archives to lore.kernel.org? Bjorn Helgaas
2022-10-12 19:15 ` Johannes Berg
2022-10-13 6:52 ` Anton Ivanov
2022-10-13 12:46 ` Richard Weinberger
2022-10-13 12:52 ` Geert Uytterhoeven
2022-10-13 12:57 ` Geert Uytterhoeven [this message]
2022-10-13 18:29 ` Konstantin Ryabitsev
2022-10-13 18:29 ` Konstantin Ryabitsev
2022-10-13 18:48 ` Geert Uytterhoeven
2022-10-13 18:48 ` Geert Uytterhoeven
2022-10-14 18:06 ` Geert Uytterhoeven
2022-10-14 18:41 ` Bjorn Helgaas
2022-11-17 8:58 ` Geert Uytterhoeven
2022-11-18 21:41 ` Konstantin Ryabitsev
2023-02-10 23:02 ` Konstantin Ryabitsev
2023-02-10 23:03 ` Bjorn Helgaas
2023-02-11 9:13 ` Richard Weinberger
2022-10-12 20:38 ` Bjorn Helgaas
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='CAMuHMdU=TurB14tkAbqb9nWYvCOcr0UUScdga25h3-oWjYfzTg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--cc=helpdesk@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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).