From: Richard Weinberger <richard@nod.at>
To: anton ivanov <anton.ivanov@cambridgegreys.com>
Cc: 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>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Add linux-um archives to lore.kernel.org?
Date: Thu, 13 Oct 2022 14:46:12 +0200 (CEST) [thread overview]
Message-ID: <2135037685.24273.1665665172126.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <f57d954a-b565-9bfa-b8eb-ce608e168f1a@cambridgegreys.com>
----- Ursprüngliche Mail -----
> Von: "anton ivanov" <anton.ivanov@cambridgegreys.com>
> On 12/10/2022 20:15, Johannes Berg wrote:
>> On Wed, 2022-10-12 at 14:11 -0500, Bjorn Helgaas wrote:
>>> The linux-um@lists.infradead.org mailing list is listed in MAINTAINERS
>>> and is quite active [1]. Once in a while a commit links to the
>>> infradead pipermail archive [2] (the link in that commit appears
>>> broken).
>>>
>>> I propose that we add linux-um to the lore.kernel.org archives so
>>> future commits can use lore.kernel.org links that don't depend on
>>> infradead.
>>>
>>> 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.
>>
>> I think we talked about this before, but I also don't have any archives
>> worth talking about (only since mid 2019 with a small gap in mid 2020).
>>
>> If anyone wants to collect the archives from all people, I'm sure it
>> could be done. I can contribute what I have ...
>>
>
> I am not keeping any (only some of the discussion on my own patches) - I relied
> on the mailing list archive.
>
>> The tooling makes that pretty simple, actually.
>>
>> I think lists.infradead.org mostly got lost though, right dwmw2? So that
>> way I don't think we'll find much (old) archives either.
Geert, IIRC you have excellent archives. Maybe you can help us?
Thanks,
//richard
next prev parent reply other threads:[~2022-10-13 12:46 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 [this message]
2022-10-13 12:52 ` Geert Uytterhoeven
2022-10-13 12:57 ` Geert Uytterhoeven
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=2135037685.24273.1665665172126.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.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 \
/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).