user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: Has anyone tried importing lkml?
Date: Mon, 15 Jan 2018 12:41:18 -0500	[thread overview]
Message-ID: <d5546b24-5840-4ae9-d25b-5e3e737ed73b@linuxfoundation.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]

Hello, all:

Every time LKML.org goes down, there's discussion about kernel.org
hosting our own public archive of LKML. There are good reasons why this
hasn't been done before, but I won't bore you with them.

The question I do have is whether public-inbox is the right tool for
doing something like this. LKML message count is somewhere in the
millions, and I'm curious what that would look like when imported into a
git tree used by public-inbox. For comparison, the Linux kernel itself
is only about 700,000 commits, so a git repo of all LKML archives would
easily dwarf that.

Has anyone tried doing this at all, or should we blaze that trail on our
own?

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 878 bytes --]

             reply	other threads:[~2018-01-15 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 17:41 Konstantin Ryabitsev [this message]
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

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=d5546b24-5840-4ae9-d25b-5e3e737ed73b@linuxfoundation.org \
    --to=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 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).