From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Mekeor Melire <mekeor@posteo.de>, help-guix <help-guix@gnu.org>
Subject: Re: This is how you import a mailing list archives (e.g. guix-patches) into mu4e
Date: Tue, 06 Dec 2022 13:03:46 +0100 [thread overview]
Message-ID: <86359skacd.fsf@gmail.com> (raw)
In-Reply-To: <87y1rlfinp.fsf@kyleam.com>
Hi Kyle,
On Mon, 05 Dec 2022 at 20:03, Kyle Meyer <kyle@kyleam.com> wrote:
> In terms of cloning archives, plain cloning and fetching with Git is
> fine, but, if you have public-inbox locally, you can instead use
> public-inbox-clone and public-inbox-fetch, which will handle some
> details for you (e.g, cloning underlying epochs and recognizing that new
> epochs have been added):
>
> $ public-inbox-clone https://yhetil.org/guix-patches
>
> Another option for fetching that's nice if you're mirror multiple repos
> is grokmirror:
>
> * https://git.kernel.org/pub/scm/utils/grokmirror/grokmirror.git/about/
> * example setup for guix: https://yhetil.org/guix-patches/878scww903.fsf@kyleam.com/
I fetch from yhetil.org (Git) and then convert to MailDir because I use
Notmuch as indexer (and reader :-)). And I do not want to duplicate the
storage. Therefore, after fetching and converting, the Git repo is
garbage collected,
--8<---------------cut here---------------start------------->8---
echo $head > $gitdir/shallow
$git gc --quiet --prune=all
--8<---------------cut here---------------end--------------->8---
https://gitlab.com/zimoun/my-conf/-/blob/master/.local/bin/sync-public-inboxes.sh#L94-99
For instance, the current size of guix-patches on my machine is 152K
compared to the complete guix-patches Git repo of 277M.
Well, I have not investigated much with ’grokmirror’ and
’public-inbox-fetch’ and maybe it would also work smoothly with the same
trick; avoiding many manual plumbing.
Thanks for sharing.
Cheers,
simon
next prev parent reply other threads:[~2022-12-06 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 23:04 This is how you import a mailing list archives (e.g. guix-patches) into mu4e Mekeor Melire
2022-11-16 23:22 ` jbranso
2022-11-16 23:41 ` Mekeor Melire
2022-12-04 20:16 ` Mekeor Melire
2022-12-05 15:39 ` Joshua Branson
2022-12-05 8:45 ` zimoun
2022-12-05 21:43 ` Mekeor Melire
2022-12-06 11:33 ` zimoun
2022-12-07 2:27 ` Mekeor Melire
2022-12-07 10:33 ` zimoun
2022-12-06 1:03 ` Kyle Meyer
2022-12-06 12:03 ` zimoun [this message]
2022-12-07 2:02 ` Kyle Meyer
2022-12-07 10:38 ` zimoun
2022-12-07 2:19 ` Mekeor Melire
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86359skacd.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=kyle@kyleam.com \
--cc=mekeor@posteo.de \
/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).