discussion and development of piem
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: Kyle Meyer <kyle@kyleam.com>, piem@inbox.kyleam.com
Subject: Re: [PATCH 4/4] Support reading inboxes from ~/.public-inbox/config
Date: Thu, 10 Jun 2021 21:32:31 +0200	[thread overview]
Message-ID: <87y2bhplbk.fsf@yoctocell.xyz> (raw)
In-Reply-To: <20210610185943.14155-5-kyle@kyleam.com>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

On Thu, Jun 10 2021, Kyle Meyer wrote:

> A client may mirror and configure inboxes locally.  Doing so enables
> fast local access to public-inbox-httpd and public-inbox-nntpd.  And
> with the next pubic-inbox release (v1.7), it will be necessary to set
> up local externals for lei.
> That can lead to a good amount of information being duplicated between
> the piem-inboxes option and ~/.public-inbox/config.  To avoid this,
> let users set an option to enable collecting information from
> public-inbox's configuration.
> This relies on code getting the list of inboxes with
> piem-merged-inboxes rather than inspecting piem-inboxes directly.
> That should be okay because at this point there should be very few
> third-party callers.  An alternative would be to merge values from the
> configuration into the value of piem-inboxes.  That'd let callers
> continue to inspect public-inboxes, but I'd prefer not to touch the
> value of a user option.
> ---
>     Xinglu, just a heads up: it looks like git-email-piem.el uses
>     piem-inboxes.  That will continue to work after this patch, but
>     it'd be good to eventually switch those spots over to calling
>     piem-merged-inboxes.

Thank you for the heads up!  I will put that on my todo list :)

BTW, I saw that you recently added an interface for lei, excited to try
it out!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2021-06-10 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 18:59 [PATCH 0/4] Support reading inboxes from ~/.public-inbox/config Kyle Meyer
2021-06-10 18:59 ` [PATCH 1/4] piem-inbox-coderepo-maybe-read: Avoid confusing "inbox" references Kyle Meyer
2021-06-10 18:59 ` [PATCH 2/4] piem-inbox-coderepo*: Always return coderepo as a directory Kyle Meyer
2021-06-10 18:59 ` [PATCH 3/4] piem-inboxes: Clarify that :coderepo points to a working tree Kyle Meyer
2021-06-10 18:59 ` [PATCH 4/4] Support reading inboxes from ~/.public-inbox/config Kyle Meyer
2021-06-10 19:32   ` Xinglu Chen [this message]
2021-06-10 21:00     ` Kyle Meyer

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:

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2bhplbk.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


* 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 public inbox


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