From: "Dom (shymega) Rodriguez" <shymega@shymega.org.uk>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Figuring out `public-inbox-fetch`
Date: Fri, 6 Sep 2024 23:42:04 +0100 [thread overview]
Message-ID: <w45eaudpggmijv2eixmzxoiyztbti6wdu5o5wsnuu6sf43e5ll@hwjefh57bvp4> (raw)
In-Reply-To: <20240905193308.M675816@dcvr>
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
On 05.09.2024 19:33, Eric Wong wrote:
>"Dom (shymega) Rodriguez" <shymega@shymega.org.uk> wrote:
>> Hi.
>>
>> I've recently been setting up a `public-inbox` mirror on my workstation.
>>
>> I've cloned the epochs for a few Linux kernel lists, and Spectrum, and
>> used `public-inbox-init` to add the lists to the configuration in
>> `$HOME`.
>>
>> However, I'm finding the documentation rather lacking (happy to make
>> patches once I figure it out) in terms of examples in some instances.
>>
>> For example, the `public-inbox-fetch` command, I've pointed the `-C`
>> argument to say, `linux-mediatek/git/0.git`, and get the following
>> output:
>>
>> ````
>> $ public-inbox-fetch -C projects/mailing-lists/linux-mediatek/git/0.git
>
>That should be pointed to the inbox directory, not the git epoch,
>(although epoch seems to work, too...):
>
>$ public-inbox-fetch -C projects/mailing-lists/linux-mediatek/
>
>You shouldn't need to go into deeper directory levels in normal day-to-day use.
Ah, okay.
>> [ ... snip ... ]
>> Am I on the right path here? I'm not sure what I'm doing wrong.
>
>I wonder if something got mangled by lore doing the redirects from http to
>https. Perhaps changing the url in git/0.git/config to use https will help
>*shrug*
Changing it to HTTPS did the trick!
>You can also try my slower lore mirror https://yhbt.net/lore/linux-mediatek/
>I use for dogfooding new changes.
>
>Also, are you using public-inbox.git or the v1.9.0 release?
>I really need to get the 2.0 features done and released but real life
>has been sucking more and more every year :x
I'm on v1.9.0 on NixOS. Is that alright to use?
>> Sorry for the 'newbie' question. Although, we all were at one point or
>> another.
>
>No worries, it's good for pointing out flaws in documentation :>
Absolutely.
>> Other than this, I'm relatively happy with `public-inbox` mirroring. I'm
>> making a developer-oriented multi-'adapter' NNTP server at the moment,
>> which I'm hoping to use myself.
>
>Cool :>
Thank you for your help :)
Best wishes,
--
Dom Rodriguez
GPG Fingerprint: EB0D 45E6 D0DC 1BA1 A2B5 FC24 72DC F123 1E54 BD43
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-07 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 18:45 Figuring out `public-inbox-fetch` Dom (shymega) Rodriguez
2024-09-05 19:33 ` Eric Wong
2024-09-06 22:42 ` Dom (shymega) Rodriguez [this message]
2024-09-07 13:54 ` 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=w45eaudpggmijv2eixmzxoiyztbti6wdu5o5wsnuu6sf43e5ll@hwjefh57bvp4 \
--to=shymega@shymega.org.uk \
--cc=e@80x24.org \
--cc=meta@public-inbox.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).