From: Yaron Scheffer <yscheffer@protonmail.com>
To: "meta@public-inbox.org" <meta@public-inbox.org>
Cc: "webmaster@lore.kernel.org" <webmaster@lore.kernel.org>
Subject: public-inbox-ssoma fails with lkml archive
Date: Tue, 23 Oct 2018 07:21:42 +0000 [thread overview]
Message-ID: <JjXMKu0VkDe80Kk7iimZx3Zld77oOzKG5UiLO-9Hc-U-gOCy7qqoYzE1xJVO6hUtKnzYTpt5DVj8NoCN9UMcprUKRYBAHrcSe0YB8P4KWFA=@protonmail.com> (raw)
Hi. I've been trying to get ssoma to fetch LKML archives into my mailbox using
the git repo at `https://lore.kernel.org/lkml/6`. Running `ssoma sync` shows
the git fetch completing successfully, but nothing shows up in my Maildir.
Performing the same procedure does however work with the PI archive at `git
://public-inbox.org/meta`.
My perl was rusty 15 years ago and it hasn't gotten any better with time,
but I've debugged this a little and the gittish things in Extractor.pm
led me to what looks like a smoking gun:
On the clone of git://public-inbox.org/meta:
# git log --name-only
commit 0fc21086aabb4ff9e9318a8ec3c6b58b24e9618a (HEAD -> master)
...
c7/16e8798bc662c5fb52d05416a27897b49f0634
commit d307195d89b21619de79722793cfaa7698aa5cf4
...
99/a639f7c6842e6c69f489f9c60af1be5e3f152d
On the clone of https://lore.kernel.org/lkml/6:
# git log --name-only
commit fa44fffb6a81e1a6b9cceccf8c08074d4d5d83ca (HEAD -> master)
...
m
commit 9845bd1f6b14185eaa77eaceea212ee0d04da673
...
m
so the lkml archive doesn't follow (mandatory, I presume) naming scheme as
PI/meta. I'm not sure if this is an issue in upstream or the deployment,
but right now ssoma doesn't work with the lkml archive.
Yaron
next reply other threads:[~2018-10-23 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 7:21 Yaron Scheffer [this message]
2018-10-23 14:33 ` public-inbox-ssoma fails with lkml archive Konstantin Ryabitsev
2018-10-23 22:47 ` Yaron Scheffer
2018-12-19 9:59 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='JjXMKu0VkDe80Kk7iimZx3Zld77oOzKG5UiLO-9Hc-U-gOCy7qqoYzE1xJVO6hUtKnzYTpt5DVj8NoCN9UMcprUKRYBAHrcSe0YB8P4KWFA=@protonmail.com' \
--to=yscheffer@protonmail.com \
--cc=meta@public-inbox.org \
--cc=webmaster@lore.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 read-only IMAP folder(s) and NNTP newsgroup(s).