linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, ben@communityfibre.ca,
	kirill@shutemov.name, mgorman@suse.de, mhocko@kernel.org,
	riel@surriel.com, daniel.m.jordan@oracle.com
Subject: linux-mm for lore.kernel.org
Date: Tue, 29 Jan 2019 10:51:28 -0500	[thread overview]
Message-ID: <20190129155128.kos4hp7rnqdg2csc@ca-dmjordan1.us.oracle.com> (raw)

Hi,

I'm working on adding linux-mm to lore.kernel.org, as previously discussed
here[1], and seem to have a mostly complete archive, starting from the
beginning in November '97.  My sources so far are the list admin's files
(thanks Ben and Rik), gmane, and my own inbox.

However, with disk corruption and downtime, it'd be great if people could pitch
in with what they have to ensure nothing is missing.  lore.kernel.org has been
archiving linux-mm since December 2018, so only messages before that date are
needed.

Instructions for contributing are here:

  https://korg.wiki.kernel.org/userdoc/lore

These are the message ids captured so far:

  https://drive.google.com/file/d/1JdpS0X1P-r0sSDg2wE1IIzrAFNN8epIE/view?usp=sharing

This uncompressed file may be passed to the -k switch of the tool in the
instructions to filter out what's already been collected.

Please tar up and xz -9 any resulting directories of mbox files and send them
to me (via sharing link if > 1M) by Feb 12, when I plan to submit the archive.

Suggestions for other sources also welcome.

Thanks,
Daniel

[1] http://lkml.kernel.org/r/20180926130850.vk6y6zxppn7bkovk@kshutemo-mobl1


             reply	other threads:[~2019-01-29 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 15:51 Daniel Jordan [this message]
2019-01-29 17:38 ` Andrew Morton
2019-01-29 18:04   ` Daniel Jordan

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=20190129155128.kos4hp7rnqdg2csc@ca-dmjordan1.us.oracle.com \
    --to=daniel.m.jordan@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@communityfibre.ca \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=riel@surriel.com \
    /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