user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: other vger lists on lore?
Date: Mon, 27 Aug 2018 16:58:11 -0400	[thread overview]
Message-ID: <20180827205811.GA1611@chatter> (raw)
In-Reply-To: <20180827205048.GA13752@dcvr>

On Mon, Aug 27, 2018 at 08:50:48PM +0000, Eric Wong wrote:
>Hi Konstantin, it looks like lore is going well for LKML :>
>
>Any plans to expand to other kernel.org lists?

Yeah, this is something I'll be actively promoting soon, but I will be 
caveating this by requesting that all lists joining lore.kernel.org 
provide an archive of messages as far back as possible. I'll probably 
start working on that in early September.

I'll follow up in a more public way once I have all the necessary bits 
done -- I need to comb over the archive sanitizing script I used for 
LKML to make it not list-specific.

>I see some messages only hit netdev or fsdevel without Cc-ing
>LKML, and it might be nice to get all of it :>
>
>/me hopes to return to more regular public-inbox hacking next week.

Nice! I don't really have any requests, except perhaps providing more 
semantic markup to the output so people interested in adding CSS bells 
and whistles can do so.

Best,
-K

  reply	other threads:[~2018-08-27 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 20:50 other vger lists on lore? Eric Wong
2018-08-27 20:58 ` Konstantin Ryabitsev [this message]
2018-09-01 20:56   ` Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180827205811.GA1611@chatter \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).