From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 4/4] Switch remaining Message-Id headers to Message-ID
Date: Sun, 30 Apr 2023 18:15:52 -0400 [thread overview]
Message-ID: <20230430221552.251335-5-kyle@kyleam.com> (raw)
In-Reply-To: <20230430221552.251335-1-kyle@kyleam.com>
The two previous commits updated the piem-add-message-id-header
functionality for git.git's change from Message-Id to Message-ID.
Updates a couple of remaining spots to use Message-ID for consistency.
---
piem.el | 2 +-
tests/piem-rmail-tests.el | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/piem.el b/piem.el
index 01985f0e..abc87b10 100644
--- a/piem.el
+++ b/piem.el
@@ -759,7 +759,7 @@ (defun piem--write-mbox-to-maildir (maildir-directory)
(save-excursion
(message-narrow-to-head-1)
(message-fetch-field "message-id" t)))
- (error "Message lacks Message-Id header")))))))
+ (error "Message lacks Message-ID header")))))))
(cl-incf n-skipped)
(let ((case-fold-search nil))
(while (re-search-forward
diff --git a/tests/piem-rmail-tests.el b/tests/piem-rmail-tests.el
index f56e2f26..7ee0a553 100644
--- a/tests/piem-rmail-tests.el
+++ b/tests/piem-rmail-tests.el
@@ -38,7 +38,7 @@ (defvar piem-rmail-tests-mbox-text "\
Cc: i@inbox.example.com
Subject: Re: test
Date: Sun, 23 May 2021 02:26:51 -0400
-Message-Id: <456@example.com>
+Message-ID: <456@example.com>
In-Reply-To: <123@example.com>
References: <123@example.com>
--
2.39.2
prev parent 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 [PATCH 0/4] Update for Git's Message-Id to Message-ID switch Kyle Meyer
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 ` Kyle Meyer [this message]
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-5-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).