b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Mailing list mirror on lore.kernel.org
Date: Fri, 06 Jan 2023 20:54:17 +0100	[thread overview]
Message-ID: <3249673.X513TT2pbd@sven-l14> (raw)

[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]

Hi,

maybe some of you remember the time when the archive of this mailing list was 
also mirrored to Gmane - providing services like web ui, nntp or raw 
(unmangled) mail downloads. But the original Gmane is gone since a long time. 
And the other public mirror (mail-archive.com) is a lot more web centric and 
not integrated in the kernel.org infrastructure.


So I spend my time between the years to fix the situation and create an 
sanitized archive of all the old mails form this mailing list. This was then 
submitted to the kernel.org's helpdesk for inclusion in their public-inbox [1]
infrastructure [2].

To make a long story short: you can now find the mails also under
https://lore.kernel.org/batman/


Some features are:

* NNTP/Atom feed support
* being able to follow threads spanning multiple (kernel) mailing lists
* handle your patch queues with b4

  For example when you want to apply the new multicast patches from Linus:

     $ b4 am 20221227193409.13461-1-linus.luessing@c0d3.blue
     $ git am ./v4_20221227_linus_luessing_implementation_of_a_stateless_multicast_packet_type.mbx

  Similar things can also be done to prepare the patches for submission.

  See

  - https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
  - https://people.kernel.org/monsieuricon/sending-a-kernel-patch-with-b4-part-1

* whole mailinglist archive available as git repository

  At the moment, our single epoch can be mirrored using:

    $ git clone --mirror https://lore.kernel.org/batman/0 batman/git/0.git
    # but you should use public-inbox/ or otherwise you might miss some 
    # archives in case it is split into multiple epochs

  See

  - https://lore.kernel.org/batman/_/text/mirror/
  - https://people.kernel.org/monsieuricon/subscribing-to-lore-lists-with-grokmirror

* Subscribe^W Pull mailing list with filters via (lore)lei

  See

  - https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started
  - https://people.kernel.org/monsieuricon/lore-lei-part-2-now-with-imap



The hyperkitty mailing archives on lists.open-mesh.org will continue to be 
supported. But their archives are not perfectly suited for working with 
patch(sets) - so this should be a nice addition for some people.

And I will also continue to use patchwork for keeping track of patches. 
lore.kernel.org and its tooling just adds a cherry on top.

Kind regards,
	Sven

[1] https://public-inbox.org/README.html
[2] https://www.kernel.org/lore.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-01-06 19:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3249673.X513TT2pbd@sven-l14 \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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.
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).