discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/3] notmuch: Improve handling of attached patches
Date: Sun, 03 Jan 2021 18:09:33 GMT	[thread overview]
Message-ID: <20210103180912.17404-1-kyle@kyleam.com> (raw)

I've hit into a few cases where piem-notmuch-am-ready-mbox hasn't been
able to find an attached patch.  This series, in particular patch 2,
should improve the situation.

  [1/3] piem-notmuch--with-current-message: Declare debug and indent specs
  [2/3] piem-notmuch-am-ready-mbox: Improve handling of attachments
  [3/3] gnus, notmuch: Absorb now-shared bits into patch attachment helper

 piem-gnus.el    | 14 ++-----------
 piem-notmuch.el | 52 ++++++++++++++++++++++++++-----------------------
 piem.el         | 21 ++++++++++++--------
 3 files changed, 43 insertions(+), 44 deletions(-)


base-commit: 96da1c622caac904e3f60e306847a4e68ca15e0c
-- 
2.29.2


             reply	other threads:[~2021-01-03 18:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 18:09 Kyle Meyer [this message]
2021-01-03 18:09 ` [PATCH 1/3] piem-notmuch--with-current-message: Declare debug and indent specs Kyle Meyer
2021-01-03 18:09 ` [PATCH 2/3] piem-notmuch-am-ready-mbox: Improve handling of attachments Kyle Meyer
2021-01-04  1:53   ` Kyle Meyer
2021-01-04  1:54     ` [PATCH v2 0/3] notmuch: Improve handling of attached patches Kyle Meyer
2021-01-04  1:54       ` [PATCH v2 1/3] piem-notmuch--with-current-message: Declare debug and indent specs Kyle Meyer
2021-01-04  1:54       ` [PATCH v2 2/3] piem-notmuch-am-ready-mbox: Improve handling of attachments Kyle Meyer
2021-01-04  1:54       ` [PATCH v2 3/3] gnus, notmuch: Absorb now-shared bits into patch attachment helper Kyle Meyer
2021-01-03 18:09 ` [PATCH " Kyle Meyer

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=20210103180912.17404-1-kyle@kyleam.com \
    --to=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).