From: Sean Whitton <spwhitton@spwhitton.name>
To: sourcehut@relevant-information.com, piem@inbox.kyleam.com
Subject: Re: [PATCH 1/1] Use notmuch-extract-patch if available
Date: Sun, 12 Dec 2021 12:26:45 -0700 [thread overview]
Message-ID: <YbZM9dHIH+lynE2o@melete.silentflame.com> (raw)
In-Reply-To: <20211209204319.168897-2-sourcehut@relevant-information.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
Hello,
On Thu, Dec 09, 2021 at 09:43:19PM +0100, Leo <sourcehut@relevant-information.com> wrote:
> From: Leo <sourcehut@relevant-information.com>
>
> notmuch-extract-patch is a command line tool from the elpa-mailscripts
> package that extracts patches from a thread. It's a useful way to
> extract the latest patch series from an email thread and filter out the
> replies and reviews.
> ---
> piem-notmuch.el | 25 +++++++++++++++++++++----
> 1 file changed, 21 insertions(+), 4 deletions(-)
>
> diff --git a/piem-notmuch.el b/piem-notmuch.el
> index 8b2a353..05c03ab 100644
> --- a/piem-notmuch.el
> +++ b/piem-notmuch.el
> + (tid
> + ;; If `notmuch-show' was called with a notmuch query rather
> + ;; than a thread ID, as `org-notmuch-follow-link' in
> + ;; org-notmuch.el does, then `notmuch-show-thread-id' might
> + ;; be an arbitrary notmuch query instead of a thread ID. We
> + ;; need to wrap such a query in thread:{} before passing it
> + ;; to notmuch-extract-patch(1), or we might not get a whole
> + ;; thread extracted (e.g. if the query is just id:foo)
This text comment is lifted straight from mailscripts.el, so please be
sure to add "(C) 2019 Sean Whitton <spwhitton@spwhitton.name" to the
copyright notices for this file. It's GPL-3+ so nothing else needed.
Glad that mailscripts.el proved useful in the development of this patch :)
--
Sean Whitton
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-12 19:26 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
2021-12-14 11:36 ` Leo
2021-12-20 6:45 ` Sean Whitton
2021-12-12 19:26 ` Sean Whitton [this message]
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=YbZM9dHIH+lynE2o@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=piem@inbox.kyleam.com \
--cc=sourcehut@relevant-information.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).