From: Kyle Meyer <kyle@kyleam.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Thiago Jung Bauermann <bauermann@kolabnow.com>,
Arun Isaac <arunisaac@systemreboot.net>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel@gnu.org
Subject: Re: public-inbox v1.7 update (was: Updating mumi on berlin)
Date: Sun, 08 May 2022 00:41:08 -0400 [thread overview]
Message-ID: <87y1zcljq3.fsf@kyleam.com> (raw)
In-Reply-To: <86tua33ydu.fsf@gmail.com>
zimoun writes:
> [...]
> Well, using the plain Git repo, it is easy to:
>
> 1. get messages from a list starting at a date;
> using ’git clone --mirror --shallow-since=’
>
> 2. get all the new messages;
> (using ’git pull)
>[...]
> IIUC, ’lei’ avoid this manual dance with the Git repo and do it for me.
It depends. Yes, you can use it in a way that avoids needing to clone
down repos and index them; in that case you're relying on the remote
instance.
Or you can clone and index the repos yourself and point lei at them.
You can do this with `lei add-external --mirror', but you still have to
update the repos yourself (see example at
<https://yhetil.org/emacs-devel/87wnh22w7o.fsf@kyleam.com>).
If you go the clone/index route, however, I'd recommend using grokmirror
to fetch Git repositories from public-inbox instances. (In
https://issues.guix.gnu.org/43637#1 <878scww903.fsf@kyleam.com/>, I
provided an example config that mirrors Guix-related inboxes at
yhetil.org.)
> Well, what I miss is the lei “saved search” query for all messages.
> Other said,
>
> lei q d:<starting-date>..
> lei up
>
> fits #1. Then, how do I achieve #2?
For remote externals, `lei up' will pull in updates from the remote.
For local externals (things you've cloned down and indexed yourself),
you need to do something to pull in those update (e.g., a grok-pull or a
`git fetch').
> The workflow using “saved search” is not clear for me. Before investing
> some time, especially when ’lei’ is not packaged in Guix, I would like
> to be sure about how to run «my workflow».
I don't regularly used saved searches myself, so I don't know that I can
be much help, even if I had a clear picture of what you wanted in your
workflow.
Fwiw my setup is:
1) use nntp via Gnus to skim new messages on mailing lists
2) if I want to participate in a thread, use
piem-inject-thread-into-maildir to get the messages into my local
mail store and my Notmuch index.
3) If I want to search for messages, I use lei-q via piem-lei-q.
Using grokmirror and a configured pull.post_update_hook, I fetch
updates for and index a subset yhetil.org inboxes that I want to
have available locally for searching.
(I use piem-inject-thread-into-maildir here too.)
I'd eventually like to be able to follow list with lei via piem's
interface, but things aren't there yet.
next prev parent reply other threads:[~2022-05-08 4:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 5:38 Updating mumi on berlin Arun Isaac
2022-04-27 6:27 ` zimoun
2022-04-27 11:14 ` Arun Isaac
2022-05-02 10:33 ` zimoun
2022-05-03 17:33 ` Arun Isaac
2022-05-03 20:42 ` Thiago Jung Bauermann
2022-05-04 8:00 ` zimoun
2022-05-05 1:49 ` Kyle Meyer
2022-05-05 3:13 ` Thiago Jung Bauermann
2022-05-05 14:45 ` Maxim Cournoyer
2022-05-06 3:16 ` Thiago Jung Bauermann
2022-05-07 22:20 ` Ludovic Courtès
2022-05-08 1:00 ` Thiago Jung Bauermann
2022-05-15 20:59 ` Ludovic Courtès
2022-05-16 8:27 ` Maxime Devos
2022-06-04 22:36 ` Thiago Jung Bauermann
2022-05-05 8:37 ` zimoun
2022-05-06 2:24 ` public-inbox v1.7 update (was: Updating mumi on berlin) Kyle Meyer
2022-05-06 7:37 ` zimoun
2022-05-08 4:41 ` Kyle Meyer [this message]
2022-05-09 13:58 ` zimoun
2022-05-06 3:22 ` Updating mumi on berlin Thiago Jung Bauermann
2022-05-06 7:48 ` zimoun
2022-05-15 22:05 ` Thiago Jung Bauermann
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=87y1zcljq3.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=arunisaac@systemreboot.net \
--cc=bauermann@kolabnow.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.