From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms12 with LMTPS id mD9rMI5OtmEaNAAAsNZ9tg (envelope-from ) for ; Sun, 12 Dec 2021 19:33:34 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id yISRK45OtmFcGgAA1q6Kng (envelope-from ) for ; Sun, 12 Dec 2021 19:33:34 +0000 Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7F018889F for ; Sun, 12 Dec 2021 20:33:33 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id C30E632004ED; Sun, 12 Dec 2021 14:33:29 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 12 Dec 2021 14:33:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spwhitton.name; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=SE7pwNLOY6FCEdsycZ0Dplrdv9B s835wrVBGC2ts9qI=; b=llw1WilqbFhl9bSqTIkvvIQPRUvI9xcXMKWdT8sSO+y yimrRwFJfpZggGSMXzDjGhNLuDZStzJbt8Uc0/NIwEUDLFYaiBdLn2f4Fih3m4TH KmrNzJJhB1gJld3GZDPAvB9quSZfYbyeob5W7AD/C7/kJ0BgzGNa6gUxAS45JCwr KL6b4F4SfGdMewX3OU7zvjYtp/mk9GZODrcUEKFUWnEfwSdw6WLn/wIBCWvk2mtP gx/xqnyGKvNEUWFROjBsyWokZoW2SwBxpMamTF0AiN9eyyGh+OMwTZ2F5dKL23j/ cx1sHY7VLsdIwlKSoK72rmqxKEP7N+z4TnI5V/+sIbA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=SE7pwN LOY6FCEdsycZ0Dplrdv9Bs835wrVBGC2ts9qI=; b=ViCL48hVNDEUPk5zp1+/6u mJ+I8n18tb6hCX5zJ95WJvdqmPj0n5lvl9xnn5VU/z8e8IPh7U7TV2UfAJuBwHJr qMk+c+OJEnRqkRdQJ9zhCsREsoqO+THnITiVPfi5T06gWqhVOcsL4FlbMeM7lH55 WpURQKiDTvYrbdNeFXJL/ph1u9izHE/GH8dGwNvxB6seQahnE+CC0NfTHV0rUGeK iOhkGxMm6pG0cJ84X8zgejgFd2rOoVQ9p6gYYvVZOubfCZT+/w2bAfQegcFA+IO0 pvsQuE1ckL/22jFohVQC5n77bL/cH169ioPcnT60rqy14KnV+Yp1brHzgelYAGGg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkeeigdduvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtddtredttddvnecuhfhrohhmpefuvggrnhcu hghhihhtthhonhcuoehsphifhhhithhtohhnsehsphifhhhithhtohhnrdhnrghmvgeqne cuggftrfgrthhtvghrnhepgefgffejfedvhedttddvgffhjeeigefhuefgjeeiteeiveeg udeujedvteeftedvnecuffhomhgrihhnpehkhihlvggrmhdrtghomhenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsphifhhhithhtohhnsehs phifhhhithhtohhnrdhnrghmvg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 12 Dec 2021 14:33:28 -0500 (EST) Received: by melete.silentflame.com (Postfix, from userid 1000) id CDD6F7E8EAF; Sun, 12 Dec 2021 12:33:27 -0700 (MST) Date: Sun, 12 Dec 2021 12:33:27 -0700 From: Sean Whitton To: Kyle Meyer Cc: Leo , piem@inbox.kyleam.com, Xinglu Chen , sgo-software-discuss@chiark.greenend.org.uk, mailscripts@packages.debian.org Subject: Re: [PATCH 1/1] Use notmuch-extract-patch if available Message-ID: References: <20211209204319.168897-1-sourcehut@relevant-information.com> <20211209204319.168897-2-sourcehut@relevant-information.com> <87mtl66ckv.fsf@kyleam.com> <87k0ga85yf.fsf@relevant-information.com> <87ilvt64rn.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="x2zuk0ITZHSEO3Bp" Content-Disposition: inline In-Reply-To: <87ilvt64rn.fsf@kyleam.com> X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -4.00 Authentication-Results: aspmx1.migadu.com; none X-Migadu-Queue-Id: 7F018889F X-Spam-Score: -4.00 X-Migadu-Scanner: scn1.migadu.com X-TUID: FVrwkyK6NVfB --x2zuk0ITZHSEO3Bp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Kyle, Leo, On Sun, Dec 12, 2021 at 01:45:48PM -0500, Kyle Meyer wrote: > [ +cc Sean for awareness, more context at > https://inbox.kyleam.com/piem/20211209204319.168897-1-sourcehut@relevan= t-information.com/T/#u ] Thank you for the CC, much appreciated. Looping in the mailing list used for mailscripts devel. > Leo writes: >=20 > > Kyle Meyer writes: > > > >> It's been a little while since I've looked over mailscripts, but I thi= nk > >> it's got a lot of neat functionality (and in general am excited to see > >> work in this space). I obviously decided to focus piem's patch > >> extraction functionality around b4, but I'm happy to consider some > >> support for notmuch-extract-patch if there are people that 1) want to > >> use notmuch-extract-patch and 2) for whatever reason, prefer to use pi= em > >> rather than mailscripts.el. > > > > I've looked a bit at mailscripts.el and it serves as a thin wrapper > > around the perl scripts in the same repo. It has two features: 1) some > > light integration with debbugs and 2) apply the patch in this > > message/thread to a repo chosen by project.el/projectile. 2) is > > basically the same as piem except that it prompts the user for a project > > (every time). > > > > I feel like there is an opportunity here to reduce > > fragmentation and make piem the main interface to mailscripts. > > mailscripts.el is very short and just with this patch it supports half > > the functionality of mailscripts.el. This would of course require > > communication with the maintainers of mailscripts and a non-trivial > > amount of work. mailscripts.el is the weakest part of mailscripts -- I think the scripts are pretty solid, but the Emacs integration is immature. If what you're suggesting here is using piem as a better Emacs frontend to the scripts, somehow subsuming mailscripts.el into piem, that sounds like it could make things better. > Given this focus, I doubt mailscripts would want to pull in piem to use > its functionality for applying patches. And at the same time, there > doesn't seem to be quite enough meat or complexity in the patch > application code that it'd be worth having an upstream library that both > piem and mailscripts could depend on. I'm not sure but I *think* what Leo is suggesting is that piem be the frontend and mailscripts' functionality gets used to apply patches ..? > My view on it at this point is that piem and mailscripts have a > different focus, and I don't think users having a few options in this > area is a bad thing. We should probably go ahead and add links to each other in the READMEs? --=20 Sean Whitton --x2zuk0ITZHSEO3Bp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmG2ToYACgkQaVt65L8G YkAYGA//YNIKKop8JryQVGspLsjSpTrmFpZ9mc6M/cno5w+o3ikDKUTFnz7fFUw2 NPE8FpTqxeTf4TIT6mocp2A2zQlV1bcMGS90ZnS9fcX+UGP5RN2y1H69FQXdcTNk 45wffm4wskvlgUwOtKo39paZZQC80CtuGFdR1LE+rp6CyKLHELjFyjA0NEtHvOmG wZQFxssey9aFyznbyveTkfXZD8HZX6NBHPJHUm5cpzJfGdFK2Gr3LXfMX1gW52gu OCBAmqa+2EnVY52wIGNgbJ98leqjrF2BH1ch1yG8nuAJdTFomBd8Hnbs+yTKWw66 jKeLC6lgMUGWQ5mRfGGhJgM/ZhZ1ctAFiYEbWmoJwd29lL9Nt+X2+6oDQTo6fXKE bA6yERiBXOO4G4wMRF8Bj53mbc6HRzeHvMaFdVGr696uc5Hw6/xw8p7kzyt6pkNX AZj+8+rreLAkY5Ujw+n9qaxoUSn1mvOTAoKW1iF8WkB9iPpJKt1B70+4xC4s8O61 AAyc441SVlD7dhfQH6ir1eU5x8kZnzJU0w7kDJfdWvrniQdTLunbV3JT/CXjpceN 4FvN/eHxxi0cuO3INOyaBkHieBwiKlHz+HvcPu4IBztew4H2BTsYFn2RSn/HSmYo kCZk6XIfxAjM6v37yjfWnwxxgaD7+XDn1Y3ELYGK+jNZgMb7mRY= =CTVl -----END PGP SIGNATURE----- --x2zuk0ITZHSEO3Bp--