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, bram.adams@polymtl.ca
Subject: Re: Has anyone tried importing lkml?
Date: Mon, 15 Jan 2018 15:09:07 -0500	[thread overview]
Message-ID: <288115d8-7e23-7e7e-8051-a2436ddb40eb@linuxfoundation.org> (raw)
In-Reply-To: <20180115182731.GA9768@80x24.org>

On 2018-01-15 01:27 PM, Eric Wong wrote:
> Also, does kernel.org have the complete archives anywhere?
> I only have the last ~4 years or so.

Let me put you in touch with someone who does.

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.

You can see the beginning of the discussion thread here:
https://public-inbox.org/meta/d5546b24-5840-4ae9-d25b-5e3e737ed73b@linuxfoundation.org/T/#u

I would be happy to act as an intermediary if you don't have a good
place to host them where they are publicly accessible.

Best,
-- 
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation

  reply	other threads:[~2018-01-15 20:09 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 [this message]
2018-01-15 20:42         ` Bram Adams
2018-01-15 20:54           ` Konstantin Ryabitsev
2018-01-15 21:03             ` Bram Adams

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=288115d8-7e23-7e7e-8051-a2436ddb40eb@linuxfoundation.org \
    --to=konstantin@linuxfoundation.org \
    --cc=bram.adams@polymtl.ca \
    --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).