From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:f42::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms12 with LMTPS id yB5oC1bLZWLBOgAAsNZ9tg (envelope-from ) for ; Sun, 24 Apr 2022 22:12:38 +0000 Received: from out1.migadu.com ([2001:41d0:2:863f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id ELP6ClbLZWI3dQAAauVa8A (envelope-from ) for ; Mon, 25 Apr 2022 00:12:38 +0200 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1650838357; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Vg7UDR5+iG4XfwE/PW4ThmX0YgVBG6ixLwzRByAc+9A=; b=j7AlnxhBL5hZuahN7oL9G4b806LkB1zhQmjFgv0RiYll1f6xljWbZMgPm8/WAq1kbq6LxQ Ma46F6r8oey5BuzX+QXLAsNXbH481F05YbxdfUY+IxZAE6q9F9gFyKZA+QPrP6yo03pZdE dDQsrXUfK5f8JcVo1MFtW3Lso8Po7fuSsgQn07cnghLZnNbQsTgpQUM3HzcADCvH2gcHHC wvs58fA2PreDv96Uhlb5/Wjhd6vHMBIx8R00WG/N2HL4rtdlOx8Ub/gFov50eGacwMhgZ2 MXSzgWVADgInhGWZRpr0WCA70ZZ2Vn05bfL3U2zTecTqMlbjqyv5gfHowLtU1A== From: Kyle Meyer To: Ihor Radchenko Cc: piem@inbox.kyleam.com Subject: Re: [FR] Support multiple repositories associated with the same ML In-Reply-To: <87v8uyncpl.fsf@localhost> References: <87v8uyncpl.fsf@localhost> Date: Sun, 24 Apr 2022 18:12:34 -0400 Message-ID: <87pml6871p.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyleam.com X-TUID: R8K9hq/m9OVW 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).