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/4] Update for Git's Message-Id to Message-ID switch
Date: Sun, 30 Apr 2023 18:15:48 -0400	[thread overview]
Message-ID: <20230430221552.251335-1-kyle@kyleam.com> (raw)

git.git's ba4324c4e1 (e-mail workflow: Message-ID is spelled with ID
in both capital letters, 2023-04-03) has been merged to master.  With
that change, format-patch will insert a Message-ID header instead of
Message-Id.

This series prepares for those changes.  The only patch that
functionally matters is patch 2, which teaches piem-am-ready-mbox's
opt-in "insert message ID header" feature to look for either spelling
when checking whether it should _not_ insert a message ID because one
already exists.

  [1/4] piem-b4-am-from-mid: Tweak docstring for consistency
  [2/4] piem-am-ready-mbox: Adjust header regex for format-patch change
  [3/4] piem-am-ready-mbox: Change spelling of inserted message ID header
  [4/4] Switch remaining Message-Id headers to Message-ID

 piem-b4.el                |  2 +-
 piem.el                   | 13 ++++++++-----
 tests/piem-rmail-tests.el |  2 +-
 tests/piem-tests.el       | 22 ++++++++++++++++++++--
 4 files changed, 30 insertions(+), 9 deletions(-)


base-commit: d78900f06615e247cee5472beca4e7ae164fe77f
-- 
2.39.2


             reply	other threads:[~2023-04-30 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 22:15 Kyle Meyer [this message]
2023-04-30 22:15 ` [PATCH 1/4] piem-b4-am-from-mid: Tweak docstring for consistency Kyle Meyer
2023-04-30 22:15 ` [PATCH 2/4] piem-am-ready-mbox: Adjust header regex for format-patch change Kyle Meyer
2023-05-01  0:22   ` Kyle Meyer
2023-04-30 22:15 ` [PATCH 3/4] piem-am-ready-mbox: Change spelling of inserted message ID header Kyle Meyer
2023-05-01  0:34   ` Kyle Meyer
2023-04-30 22:15 ` [PATCH 4/4] Switch remaining Message-Id headers to Message-ID 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=20230430221552.251335-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).