From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <Bart.VanAssche@wdc.com>, "hch@lst.de" <hch@lst.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Archiving linux-block
Date: Wed, 6 Sep 2017 08:10:51 -0600 [thread overview]
Message-ID: <d3e438ca-5d6e-b790-a42e-1927474d7042@kernel.dk> (raw)
In-Reply-To: <1504703610.7750.3.camel@wdc.com>
On 09/06/2017 07:13 AM, Bart Van Assche wrote:
> On Tue, 2017-09-05 at 08:33 -0600, Jens Axboe wrote:
>> On 09/05/2017 08:19 AM, Bart Van Assche wrote:
>>> Since gmane.org is no longer operational linux-block messages are no longer
>>> archived. I think it's useful to archive linux-block messages because it
>>> makes it possible to review past discussions, especially for people who are
>>> not subscribed to the list. How about activating archival by mail-archive.com
>>> and spinics.net? As far as I know this can only be done by someone who is list
>>> administrator. But I don't know who the linux-block list administrator(s) are?
>>
>> I always use marc.info:
>>
>> https://marc.info/?l=linux-block
>>
>> If we want to add it elsewhere, that's fine with me. I'm probably the admin,
>> I was the one that asked for the list to be created.
>
> Thanks Jens for the feedback. What I tried yesterday morning was to look up a
> linux-block message by searching for its contents with a web search engine. That
> search did not yield any results. Does this mean that messages on marc.info are
> not indexed by Google? Is this a sufficient reason to let an additional web site
> archive the linux-block messages?
Definitely, it'd be nice to have it be searchable. That's half the utility of
an archive...
I'll see if I can get mail-archive.com setup.
--
Jens Axboe
next prev parent reply other threads:[~2017-09-06 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 14:19 Archiving linux-block Bart Van Assche
2017-09-05 14:33 ` Jens Axboe
2017-09-06 13:13 ` Bart Van Assche
2017-09-06 14:10 ` Jens Axboe [this message]
2017-09-06 14:13 ` Jens Axboe
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=d3e438ca-5d6e-b790-a42e-1927474d7042@kernel.dk \
--to=axboe@kernel.dk \
--cc=Bart.VanAssche@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.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