From: Leo <sourcehut@relevant-information.com>
To: Sean Whitton <spwhitton@spwhitton.name>, Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com, Xinglu Chen <public@yoctocell.xyz>,
sgo-software-discuss@chiark.greenend.org.uk,
mailscripts@packages.debian.org
Subject: Re: [PATCH 1/1] Use notmuch-extract-patch if available
Date: Mon, 13 Dec 2021 12:45:09 +0100 [thread overview]
Message-ID: <87wnk8k9tm.fsf@student-238-188.eduroam.uu.se> (raw)
In-Reply-To: <YbZOh0yEFLBwVUMp@melete.silentflame.com>
Sean Whitton <spwhitton@spwhitton.name> writes:
> On Sun, Dec 12, 2021 at 01:45:48PM -0500, Kyle Meyer wrote:
>
>> 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 ..?
>
Yeah, pretty much. Piem already feels pretty general with support for
gnus, notmuch, b4, eww and elfeed so adding mailscripts doesn't feel
like a big leap.
next prev parent reply other threads:[~2021-12-13 11:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 20:43 [PATCH 0/1] Use notmuch-extract-patch if available sourcehut
2021-12-09 20:43 ` [PATCH 1/1] " sourcehut
2021-12-11 21:44 ` Kyle Meyer
2021-12-12 9:44 ` Leo
2021-12-12 18:45 ` Kyle Meyer
2021-12-12 19:33 ` Sean Whitton
2021-12-12 19:49 ` Kyle Meyer
2021-12-14 19:12 ` Sean Whitton
2021-12-13 11:45 ` Leo [this message]
2021-12-14 11:36 ` Leo
2021-12-20 6:45 ` Sean Whitton
2021-12-12 19:26 ` Sean Whitton
2021-12-13 11:53 ` Leo
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=87wnk8k9tm.fsf@student-238-188.eduroam.uu.se \
--to=sourcehut@relevant-information.com \
--cc=kyle@kyleam.com \
--cc=mailscripts@packages.debian.org \
--cc=piem@inbox.kyleam.com \
--cc=public@yoctocell.xyz \
--cc=sgo-software-discuss@chiark.greenend.org.uk \
--cc=spwhitton@spwhitton.name \
/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).