unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: zimoun <zimon.toutoune@gmail.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 21:02:42 -0500	[thread overview]
Message-ID: <87tu28ezst.fsf@kyleam.com> (raw)
In-Reply-To: <86359skacd.fsf@gmail.com>

zimoun writes:

> 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.

Nice.  Maintaining a shallow clone certainly makes sense.

> 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.

I haven't used it myself (unsurprisingly I have an interest in keeping
yhetil.org's inboxes replicated on my local machine), but I think you
can keep grokmirror clones shallow by hooking up its grok-pi-piper to
the post-update hook. Here's a relevant bit from grokmirror's docs:

--8<---------------cut here---------------start------------->8---
[DEFAULT]
# To start piping public-inbox messages into your inbox, simply
# install procmail and add the following line to your ~/.procmailrc:
#     DEFAULT=$HOME/Maildir/
# You can now read your mail with "mutt -f ~/Maildir/"
pipe = /usr/bin/procmail
# Once you've successfully piped the messages, you generally
# don't need them any more. If you set shallow = yes, then
# the repository will be configured as "shallow" and all succesffully
# processed messages will be pruned from the repo.
# This will greatly reduce disk space usage, especially on large archives.
# You can always get any number of them back, e.g. by running:
# git fetch _grokmirror master --deepen 100
shallow = yes
--8<---------------cut here---------------end--------------->8---


  reply	other threads:[~2022-12-07  2:03 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
2022-12-07  2:02       ` Kyle Meyer [this message]
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=87tu28ezst.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=help-guix@gnu.org \
    --cc=mekeor@posteo.de \
    --cc=zimon.toutoune@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).