user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Bram Adams <bram.adams@polymtl.ca>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: Has anyone tried importing lkml?
Date: Mon, 15 Jan 2018 16:03:49 -0500	[thread overview]
Message-ID: <55B7E1B4-FAA9-4307-8A9C-C3483D803004@polymtl.ca> (raw)
In-Reply-To: <443422ec-49a6-d703-0e12-42ef79ef8081@linuxfoundation.org>

Hi,

>>> Bram, we're looking at various available options for hosting publicly
>>> accessible archives of LKML, together with a searchable/threadable web
>>> frontend. I know this is directly related to the work you've been doing
>>> with cregit, and I wonder if you would be able to provide Eric with full
>>> LKML archives for some initial testing. It's probably something cregit
>>> can benefit from, too, should we start providing this service.
>> 
>> Yes, we have a copy of the full history until August 2016 of LKML and 130 other mailing lists in mbox form. They are on the cregit server you provided us.
> 
> Found them. Is October 2000 the beginning of LKML, or just the beginning
> of the archive? I'm actually unsure of the history of the list. :)

It’s the second option, i.e., beginning of the archive. LKML goes back to 1996, see https://lkml.org/lkml (in fact 1910, but that’s probably not correct :-)).

> 
>> From cregit’s point of view, we are interested in any form of email archive that:
>> * is up-to-date
>> * parses the emails into metadata, patches, patch series, …
>> * is quick to query
> 
> Looks like we're getting unblocked for these resources, so we may be
> able to set up that LKML-specific patchwork instance for you -- but
> that's a separate thread that should probably stay off this list.

Cool, thanks!

Kind regards,

Bram Adams

      reply	other threads:[~2018-01-15 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 17:41 Has anyone tried importing lkml? Konstantin Ryabitsev
2018-01-15 17:55 ` Eric Wong
2018-01-15 18:04   ` Konstantin Ryabitsev
2018-01-15 18:27     ` Eric Wong
2018-01-15 20:09       ` Konstantin Ryabitsev
2018-01-15 20:42         ` Bram Adams
2018-01-15 20:54           ` Konstantin Ryabitsev
2018-01-15 21:03             ` Bram Adams [this message]

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=55B7E1B4-FAA9-4307-8A9C-C3483D803004@polymtl.ca \
    --to=bram.adams@polymtl.ca \
    --cc=e@80x24.org \
    --cc=konstantin@linuxfoundation.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).