We collect kernel archives on lore.kernel.org using software called public-inbox. While any mailing list that is used for Linux kernel development can qualify, we give priority to mailing lists served via vger.kernel.org.
Since vger.kernel.org has existed for over 20 years, there is one important caveat we require before adding an existing list to lore.kernel.org – you must provide as complete of an archive as possible. This wiki page describes the best procedure to follow.
You will need to provide an as-complete-as-possible archive of list messages. If you have been subscribed to the list for a while, you can start with your own archives.
If you've been subscribed to the list via GMail, it is very easy to collect the initial set of archives.
Wait till you receive the download link email (may take a while) and follow the instructions you receive. The archive should contain one or several files in .mbox format that you need. Extract them and proceed to the next section.
We provide a list-archive-maker script that will remove unnecessary headers from the mbox file and make sure that all messages in it belong to the mailing list.
Example with email@example.com:
mkdir ~/linux-kernel-announce ./list-archive-maker.py -s export-linux-kernel-announce.mbox \ -e ~/linux-kernel-announce \ -k ~/linux-kernel-announce-known-ids.txt \ -l linux-kernel-announce.vger.kernel.org
This will sanitize the archives and put them into ~/linux-kernel-announce in your home directory.
Once you have your initial archive, you can solicit donated archives from others, who may have been subscribed to the list for longer, or have messages that did not get delivered to you for some reason.
You will need the know-ids.txt file from the previous step, to make sure that others don't send you messages you already have.
Send a message to the list, something like this (edit to your liking):
Hi, everyone: I'm working to add this list to lore.kernel.org. As one of prerequisites they require that we provide full existing archives of all list messages (or, at least, as complete as possible). I've collected mine already, but would really appreciate if you could pitch in from your own collection. Just follow the instructions on this page: https://korg.wiki.kernel.org/userdoc/lore I've attached the list of message-ids that I already have. You'll need it during the archive sanitization process to pass to the -k switch. Please tar up and xz -9 the resulting directory with mbox files and send the archive to me so I can add it to what I already have. Thanks!
If you receive any archives, you can merge them with what you already have using the same script. Make sure you're pointing at the same known-ids.txt file as the one you attached to the solicitation email, otherwise you will have unnecessary duplicate entries.
./list-archive-maker.py -s dir-with-mbox-files/* \ -e ~/linux-kernel-announce \ -k ~/linux-kernel-announce-known-ids.txt \ -l linux-kernel-announce.vger.kernel.org
Once you've done your best collecting archives, tar them up and compress them:
tar cf full-archives.tar dir-with-mbox-files xz -9 full-archives.tar
If the resulting file is smaller than a few MB, you can attach it to the follow-up email to firstname.lastname@example.org. If the archive is larger than that, please upload it to a file sharing service, such as Google Drive:
The kernel.org administrators will combine the archive they receive from you with the messages they have pre-collected, to make sure there is no interruption between when your archive collection was completed and when public-inbox starts receiving new messages. You will be notified when the mailing list is ready to be accessed via lore.kernel.org.
We *can* use mailman's pipermail archives, but it's best if it's done as a final filler for anything not collected elsewhere, for these reasons:
We suggest you proceed with archive collection per above, and then fill in any missing bits with pipermail archives as the last step (the list-archive-marker.py script has automated functionality to do this).