discussion and development of piem
 help / color / mirror / code / Atom feed
From: Leo <sourcehut@relevant-information.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH 1/1] Use notmuch-extract-patch if available
Date: Sun, 12 Dec 2021 10:44:11 +0100	[thread overview]
Message-ID: <87k0ga85yf.fsf@relevant-information.com> (raw)
In-Reply-To: <87mtl66ckv.fsf@kyleam.com>


Kyle Meyer <kyle@kyleam.com> writes:

>
> It's been a little while since I've looked over mailscripts, but I think
> 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 piem
> 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.

I'll get back to the comments on the patch later.


--
---Leo

  reply	other threads:[~2021-12-12 10:37 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 [this message]
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
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=87k0ga85yf.fsf@relevant-information.com \
    --to=sourcehut@relevant-information.com \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.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).