The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-parport@lists.infradead.org
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Tim Waugh <tim@cyberelk.net>,
	linux-parport-owner@lists.infradead.org,
	linux-kernel@vger.kernel.org, helpdesk@kernel.org
Subject: Re: Add linux-parport archives to lore.kernel.org?
Date: Wed, 12 Oct 2022 15:37:05 -0500	[thread overview]
Message-ID: <20221012203705.GA3117743@bhelgaas> (raw)
In-Reply-To: <20221012191201.GA3107702@bhelgaas>

On Wed, Oct 12, 2022 at 02:12:03PM -0500, Bjorn Helgaas wrote:
> The linux-parport@lists.infradead.org mailing list is listed in
> MAINTAINERS.  There's not much current activity [1], but I suspect
> there's some useful history that we might want to preserve.
> 
> Should we add linux-parport to the lore.kernel.org archives?
> 
> 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.

FWIW, here's a link to pipermail "archives" downloaded with:
  wget -r -np -l 1 -n d -A gz http://lists.infradead.org/pipermail/$LIST/
  tar cf $LIST.tar $LIST
  xz -9 $LIST.tar

https://drive.google.com/file/d/1rS8r7M0fs18k6ehdLp9cgwYMPZIhCRKI/view?usp=sharing

  reply	other threads:[~2022-10-12 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 19:12 Add linux-parport archives to lore.kernel.org? Bjorn Helgaas
2022-10-12 20:37 ` Bjorn Helgaas [this message]
2022-10-12 20:56 ` Sudip Mukherjee
2022-10-13  0:08   ` [Linux-parport] " Info Skymem
2022-10-13 18:29 ` Konstantin Ryabitsev

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=20221012203705.GA3117743@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=helpdesk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport-owner@lists.infradead.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tim@cyberelk.net \
    /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