discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Cc: jlicht@fsfe.org
Subject: [ANNOUNCE] piem v0.5.0
Date: Sun, 18 Jun 2023 12:39:41 -0400	[thread overview]
Message-ID: <87zg4wlo6q.fsf@kyleam.com> (raw)

piem v0.5.0 has been released, with a corresponding tag pushed to
<https://git.kyleam.com/piem/>.  It consists of 22 non-merge commits
since v0.4.0 contributed by Jelle Licht and Kyle Meyer.

Bug reports, patches, questions, and other feedback are welcome.  Please
send a plain-text email to


Messages that include this address are public and available as
public-inbox archives at



piem v0.5.0 release notes

Changes since v0.4.0

 * New library piem-debbugs.el provides Debbugs mode integration.

 * New :gnu-package property enables mapping a message to an inbox via
   the X-GNU-PR-Package header (present on <https://bugs.gnu.org>

 * An inbox can now be linked to multiple repositories by setting
   :coderepo to a list.

 * :url values in piem-inboxes no longer require a trailing slash.

 * piem-inject-thread-into-maildir gained an INBOX argument to enable
   Lisp callers to specify an inbox.  Thanks to zimoun for the

 * The piem-b4-am transient now includes --cc-trailers (added in b4

 * The logic to insert a Message-ID header when
   piem-add-message-id-header is non-nil has been updated to account
   for a recent change in how Git spells the header.

 * piem-am now reorders attachments to be more helpful in cases where
   the sender attaches the patches out of order.  Thanks for Ihor
   Radchenko for the suggestion.

Fixes since v0.4.0

 * piem-gnus-mid-to-thread didn't consider that
   gnus-summary-display-article may dump a message in mbox format.


Jelle Licht (5):
      piem: Add :gnu-package keyword to piem-inboxes
      gnus: Skip adding mboxrd from-line when not needed
      piem: Add piem-inbox-by-gnu-package-match
      piem-inbox-by-header-match: Fallback to matching via :gnu-package
      Add basic integration for debbugs

Kyle Meyer (17):
      piem-inboxes: Support mapping inbox to multiple coderepos
      TODO: mention Ihor's suggestion for reapply behavior
      piem-inject-thread-into-maildir: Let Lisp callers specify inbox
      piem-b4-am: Move trailer-related options to dedicated section
      piem-b4-am: Add --cc-trailers
      piem--write-mbox-to-maildir: Tweak error message
      gnus: Call message-field-value with lower case header
      piem-am: Order attached patches by file name prefix
      piem-rmail-tests.el: Silence rmail-mode messages
      piem-b4-am-from-mid: Tweak docstring for consistency
      piem-am-ready-mbox: Adjust header regex for format-patch change
      piem-am-ready-mbox: Change spelling of inserted message ID header
      Switch remaining Message-Id headers to Message-ID
      piem-inbox-by-header-match: Fix docstring reference
      piem-inboxes: Allow :url values without a trailing slash
      .guix.scm: Update for upstream inclusion
      Release version 0.5.0

                 reply	other threads:[~2023-06-18 16:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  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=87zg4wlo6q.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=jlicht@fsfe.org \
    --cc=piem@inbox.kyleam.com \


* 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


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).