From: Luis Chamberlain <mcgrof@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: grokmirror and pi-piper for all emails on a list
Date: Fri, 28 May 2021 15:42:58 -0700 [thread overview]
Message-ID: <CAB=NE6VF1W-Wdp9+cmb-ehJ2Gf5_1yqYxNd1qp3Z=acgbYUe3w@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6X5uUWA7Sfu_qvz2smddgc4euBT-x7xGs8=7+K-W5v2RQ@mail.gmail.com>
On Fri, May 28, 2021 at 1:46 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> Figured folks might be interested... it took only about 5 minutes on
> the first run, the second run, with my settings took about 8 minutes.
> Not too shabby (nvme drives)!
It ran fast as it only processed lkml, but 8 minutes for processing
the latest epoch for lkml is also not too bad. Anyway let me know if
anyone has any idea of the following:
So after some debugging I am seeing that with a setup as follows,
running grok-pull -c ~/.config/lore.conf seems to not run pi-piper if
any of the repos being processed doesn't need an update. If I actually
also force the pi-paper.latest to each repo to say, the last 3rd
commit, I still don't see the last 3 emails coming up. But if I run
manually against reach repo like this:
grok-pi-piper -c ~/.config/pi-piper.conf
.local/share/grokmirror/lore/linux-fsdevel/git/0.git/
Then it triggers it to deliver mail as expected. So I am thinking the
following config may be missing something to force the post hook to
really run for each repo, or there may be a bug somewhere. I removed
the new lines from the include as it was not clear if having each
target repo per line is fine. And if you have each repo, if spaces are
allowed, or tabs are allowed.
$ cat .config/lore.conf
[core]
toplevel = ~/.local/share/grokmirror/lore
log = ${toplevel}/grokmirror.log
[remote]
site = https://lore.kernel.org
manifest = https://lore.kernel.org/manifest.js.gz
[pull]
post_update_hook = ~/.local/bin/grok-pi-piper -c ~/.config/pi-piper.conf
refresh = 300
include = /linux-fsdevel/* /linux-block/* /linux-btrfs/* /linux-xfs/* /lkml/*
next prev parent reply other threads:[~2021-05-28 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 19:14 grokmirror and pi-piper for all emails on a list Luis Chamberlain
2021-05-28 19:38 ` Konstantin Ryabitsev
2021-05-28 19:46 ` Luis Chamberlain
2021-05-28 19:53 ` Konstantin Ryabitsev
2021-05-28 20:34 ` Luis Chamberlain
2021-05-28 20:46 ` Luis Chamberlain
2021-05-28 22:42 ` Luis Chamberlain [this message]
2021-05-28 21:09 ` Konstantin Ryabitsev
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='CAB=NE6VF1W-Wdp9+cmb-ehJ2Gf5_1yqYxNd1qp3Z=acgbYUe3w@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.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 NNTP newsgroup(s).