diff for duplicates of <036301da5dfd$be7d1b30$3b775190$@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 05f926b..3446125 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -26,3 +26,8 @@ since anyone trying to use it would run into interop issues because
 of existing clang.   Should we document both and list one as deprecated?
 
 Dave
+
+-- 
+Bpf mailing list
+Bpf@ietf.org
+https://www.ietf.org/mailman/listinfo/bpf
diff --git a/a/content_digest b/N1/content_digest
index 62eddfb..b646232 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,8 @@
  "ref\020240212211310.8282-1-dthaler1968@gmail.com\0"
  "ref\087le7ptlsq.fsf@oracle.com\0"
  "ref\0b5072dfb-ab2b-40eb-891e-630a02c58fe8@linux.dev\0"
- "From\0dthaler1968@googlemail.com\0"
- "Subject\0RE: [Bpf] [PATCH bpf-next v2] bpf, docs: Add callx instructions in new conformance group\0"
+ "From\0dthaler1968=40googlemail.com@dmarc.ietf.org\0"
+ "Subject\0Re: [Bpf] [PATCH bpf-next v2] bpf, docs: Add callx instructions in new conformance group\0"
  "Date\0Mon, 12 Feb 2024 13:52:15 -0800\0"
  "To\0'Yonghong Song' <yonghong.song@linux.dev>"
   'Jose E. Marchesi' <jose.marchesi@oracle.com>
@@ -38,6 +38,11 @@
  "since anyone trying to use it would run into interop issues because\n"
  "of existing clang.   Should we document both and list one as deprecated?\n"
  "\n"
- Dave
+ "Dave\n"
+ "\n"
+ "-- \n"
+ "Bpf mailing list\n"
+ "Bpf@ietf.org\n"
+ https://www.ietf.org/mailman/listinfo/bpf
 
-a5dc4c429a61003d3191d5e74b5a0dac090e6cd4ab556c7dcc5acf7eead9756c
+2bcc0a03308677f2a5c946fbb339665f8079d495c86b72b0c63168a782ad199a
