From: Kyle Meyer <kyle@kyleam.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [FR] Support multiple repositories associated with the same ML
Date: Sun, 24 Apr 2022 18:12:34 -0400 [thread overview]
Message-ID: <87pml6871p.fsf@kyleam.com> (raw)
In-Reply-To: <87v8uyncpl.fsf@localhost>
Hi Ihor,
Ihor Radchenko writes:
> Hi,
>
> I am currently using piem to work with Org mode ML and quite enjoying
> it.
I'm glad to hear that (and thank you for all of the Org work you've been
doing).
> However, I just ran into an issue related to the fact that Org ML is
> used to manage multiple repositories.
>
> Org mode ML is an official mailing list for Org mode itself,
> org-contrib, worg, and main Org website repositories. We accept patches
> for all these projects in the same ML. Running piem-am when I configure
> piem-inboxes to point to the same ML for different repos only considers
> the first matching repo and does not query me where to apply the patch.
Right, I'd like piem to cover this use case. Here's a relevant to-do
comment in piem.el:
;; TODO: Decide how to deal with inboxes that map to more than one
;; coderepo. This is important to support for people that want to
;; use a catchall inbox for small projects which they don't think
;; (yet) need a dedicated address.
(defcustom piem-inboxes nil
I'll plan to take a look at this soon (within the next week or two).
next prev parent reply other threads:[~2022-04-24 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 7:48 [FR] Support multiple repositories associated with the same ML Ihor Radchenko
2022-04-24 22:12 ` Kyle Meyer [this message]
2022-04-26 9:19 ` Applying the same patch multiple times (was: [FR] Support multiple repositories associated with the same ML) Ihor Radchenko
2022-04-27 3:49 ` Applying the same patch multiple times Kyle Meyer
2022-04-27 12:46 ` Ihor Radchenko
2022-05-07 14:19 ` Kyle Meyer
2022-05-06 1:40 ` [PATCH] piem-inboxes: Support mapping inbox to multiple coderepos Kyle Meyer
2022-05-06 2:10 ` Ihor Radchenko
2022-05-06 3:28 ` Kyle Meyer
2022-05-07 5:21 ` Ihor Radchenko
2022-05-07 14:18 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87pml6871p.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=piem@inbox.kyleam.com \
--cc=yantar92@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 public inbox
https://git.kyleam.com/piem/
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).