diff for duplicates of <20210511110002.2f187f01@coco.lan>

diff --git a/a/1.txt b/N1/1.txt
index 809ead5..fb113c7 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -12,7 +12,7 @@ Edward Cree <ecree.xilinx@gmail.com> escreveu:
 Sorry for the mess. The main reason why I wrote this series is because
 there are lots of UTF-8 left-over chars from the ReST conversion.
 See:
-  - https://lore.kernel.org/linux-doc/20210507100435.3095f924@coco.lan/
+  - https://lore.kernel.org/linux-doc/20210507100435.3095f924 at coco.lan/
 
 A large set of the UTF-8 letf-over chars were due to my conversion work,
 so I feel personally responsible to fix those ;-)
@@ -35,7 +35,7 @@ FYI, this patch series originated from a discussion at linux-doc,
 reporting that Sphinx breaks when LANG is not set to utf-8[2]. That's
 why I probably ended giving the wrong emphasis at the cover letter.
 
-[2] See https://lore.kernel.org/linux-doc/20210506103913.GE6564@kitsune.suse.cz/
+[2] See https://lore.kernel.org/linux-doc/20210506103913.GE6564 at kitsune.suse.cz/
     for the original report. I strongly suspect that the VM set by Michal 
     to build the docs was using a distro that doesn't set UTF-8 as default.
 
@@ -71,7 +71,7 @@ one) would type a NO-BREAK SPACE instead of a normal white space.
 The same applies, up to some sort, to curly commas: usually people just 
 write ASCII "commas" on their documents, and use some tool like LaTeX
 or a text editor like libreoffice in order to convert them into
- “utf-8 curly commas”[3].
+ ?utf-8 curly commas?[3].
 
 [3] Sphinx will do such things at the produced output, doing something 
     similar to what smartypants does, nowadays using this:
diff --git a/a/content_digest b/N1/content_digest
index c7e8362..2903e36 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,42 +5,9 @@
  "ref\0YJk8LMFViV7Z3Uu7@casper.infradead.org\0"
  "ref\0ed65025c-1087-9672-7451-6d28e7ab8f92@gmail.com\0"
  "From\0Mauro Carvalho Chehab <mchehab+huawei@kernel.org>\0"
- "Subject\0Re: [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII\0"
+ "Subject\0[Intel-wired-lan] [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII\0"
  "Date\0Tue, 11 May 2021 11:00:02 +0200\0"
- "To\0Edward Cree <ecree.xilinx@gmail.com>\0"
- "Cc\0alsa-devel@alsa-project.org"
-  kvm@vger.kernel.org
-  Linux Doc Mailing List <linux-doc@vger.kernel.org>
-  linux-iio@vger.kernel.org
-  linux-pci@vger.kernel.org
-  linux-fpga@vger.kernel.org
-  dri-devel@lists.freedesktop.org
-  keyrings@vger.kernel.org
-  linux-riscv@lists.infradead.org
-  Jonathan Corbet <corbet@lwn.net>
-  linux-rdma@vger.kernel.org
-  x86@kernel.org
-  Matthew Wilcox <willy@infradead.org>
-  linux-acpi@vger.kernel.org
-  intel-wired-lan@lists.osuosl.org
-  linux-input@vger.kernel.org
-  linux-ext4@vger.kernel.org
-  intel-gfx@lists.freedesktop.org
-  linux-media@vger.kernel.org
-  linux-pm@vger.kernel.org
-  linux-sgx@vger.kernel.org
-  coresight@lists.linaro.org
-  rcu@vger.kernel.org
-  mjpeg-users@lists.sourceforge.net
-  linux-arm-kernel@lists.infradead.org
-  linux-edac@vger.kernel.org
-  linux-hwmon@vger.kernel.org
-  netdev@vger.kernel.org
-  linux-usb@vger.kernel.org
-  linux-kernel@vger.kernel.org
-  linux-f2fs-devel@lists.sourceforge.net
-  linux-integrity@vger.kernel.org
- " David Woodhouse <dwmw2@infradead.org>\0"
+ "To\0intel-wired-lan@osuosl.org\0"
  "\00:1\0"
  "b\0"
  "Em Mon, 10 May 2021 15:33:47 +0100\n"
@@ -57,7 +24,7 @@
  "Sorry for the mess. The main reason why I wrote this series is because\n"
  "there are lots of UTF-8 left-over chars from the ReST conversion.\n"
  "See:\n"
- "  - https://lore.kernel.org/linux-doc/20210507100435.3095f924@coco.lan/\n"
+ "  - https://lore.kernel.org/linux-doc/20210507100435.3095f924 at coco.lan/\n"
  "\n"
  "A large set of the UTF-8 letf-over chars were due to my conversion work,\n"
  "so I feel personally responsible to fix those ;-)\n"
@@ -80,7 +47,7 @@
  "reporting that Sphinx breaks when LANG is not set to utf-8[2]. That's\n"
  "why I probably ended giving the wrong emphasis at the cover letter.\n"
  "\n"
- "[2] See https://lore.kernel.org/linux-doc/20210506103913.GE6564@kitsune.suse.cz/\n"
+ "[2] See https://lore.kernel.org/linux-doc/20210506103913.GE6564 at kitsune.suse.cz/\n"
  "    for the original report. I strongly suspect that the VM set by Michal \n"
  "    to build the docs was using a distro that doesn't set UTF-8 as default.\n"
  "\n"
@@ -116,7 +83,7 @@
  "The same applies, up to some sort, to curly commas: usually people just \n"
  "write ASCII \"commas\" on their documents, and use some tool like LaTeX\n"
  "or a text editor like libreoffice in order to convert them into\n"
- " \342\200\234utf-8 curly commas\342\200\235[3].\n"
+ " ?utf-8 curly commas?[3].\n"
  "\n"
  "[3] Sphinx will do such things at the produced output, doing something \n"
  "    similar to what smartypants does, nowadays using this:\n"
@@ -160,4 +127,4 @@
  "Thanks,\n"
  Mauro
 
-43dff3f3cadaf38b090a62dd1c9ba83a1bdb2381a2db92284c430ac20649b166
+9589c67c51e803ad2fad510e088f4a382b98a0f3bde3578478f6148b1bd45a25
