diff for duplicates of <CAKOZuesQXRtthJTEr86LByH3gPpAdT-PQM0d1jqr131=zZNRKw@mail.gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 1e58160..8af985d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,15 +1,15 @@
-On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel@joelfernandes.org> wrote:
+On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel at joelfernandes.org> wrote:
 > Thanks Andy for your thoughts, my comments below:
 >
 > On Fri, Nov 09, 2018 at 10:05:14PM -0800, Andy Lutomirski wrote:
 >>
 >>
->> > On Nov 9, 2018, at 7:20 PM, Joel Fernandes <joel@joelfernandes.org> wrote:
+>> > On Nov 9, 2018, at 7:20 PM, Joel Fernandes <joel at joelfernandes.org> wrote:
 >> >
 >> >> On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote:
->> >>> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh@google.com> wrote:
+>> >>> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh at google.com> wrote:
 >> >>> On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google)
->> >>> <joel@joelfernandes.org> wrote:
+>> >>> <joel at joelfernandes.org> wrote:
 >> >>>> Android uses ashmem for sharing memory regions. We are looking forward
 >> >>>> to migrating all usecases of ashmem to memfd so that we can possibly
 >> >>>> remove the ashmem driver in the future from staging while also
@@ -36,13 +36,13 @@ On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel@joelfernandes.org> wrote:
 >> >>>> The following program shows the seal
 >> >>>> working in action:
 >> >>> [...]
->> >>>> Cc: jreck@google.com
->> >>>> Cc: john.stultz@linaro.org
->> >>>> Cc: tkjos@google.com
->> >>>> Cc: gregkh@linuxfoundation.org
->> >>>> Cc: hch@infradead.org
->> >>>> Reviewed-by: John Stultz <john.stultz@linaro.org>
->> >>>> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
+>> >>>> Cc: jreck at google.com
+>> >>>> Cc: john.stultz at linaro.org
+>> >>>> Cc: tkjos at google.com
+>> >>>> Cc: gregkh at linuxfoundation.org
+>> >>>> Cc: hch at infradead.org
+>> >>>> Reviewed-by: John Stultz <john.stultz at linaro.org>
+>> >>>> Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>
 >> >>>> ---
 >> >>> [...]
 >> >>>> diff --git a/mm/memfd.c b/mm/memfd.c
@@ -116,7 +116,7 @@ On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel@joelfernandes.org> wrote:
 >> > to the new fix? The patch is based on top of this series.
 >> >
 >> > ---8<-----------
->> > From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
+>> > From: "Joel Fernandes (Google)" <joel at joelfernandes.org>
 >> > Subject: [PATCH] mm/memfd: Fix possible promotion to writeable of sealed memfd
 >> >
 >> > Jann Horn found that reopening an F_SEAL_FUTURE_WRITE sealed memfd
@@ -124,8 +124,8 @@ On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel@joelfernandes.org> wrote:
 >> > without causing ABI breakages and ugly VFS hacks is to simply deny all
 >> > opens on F_SEAL_FUTURE_WRITE sealed fds.
 >> >
->> > Reported-by: Jann Horn <jannh@google.com>
->> > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
+>> > Reported-by: Jann Horn <jannh at google.com>
+>> > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>
 >> > ---
 >> > mm/shmem.c | 18 ++++++++++++++++++
 >> > 1 file changed, 18 insertions(+)
diff --git a/a/content_digest b/N1/content_digest
index 923039f..330cf22 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,43 +17,14 @@
   "ref\00020181110182405.GB242356\@google.com\0"
 ]
 [
-  "From\0Daniel Colascione <dancol\@google.com>\0"
+  "From\0dancol at google.com (Daniel Colascione)\0"
 ]
 [
-  "Subject\0Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0"
+  "Subject\0[PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0"
 ]
 [
   "Date\0Sat, 10 Nov 2018 10:45:19 -0800\0"
 ]
-[
-  "To\0Joel Fernandes <joel\@joelfernandes.org>\0"
-]
-[
-  "Cc\0Andy Lutomirski <luto\@amacapital.net>",
-  " Jann Horn <jannh\@google.com>",
-  " kernel list <linux-kernel\@vger.kernel.org>",
-  " John Reck <jreck\@google.com>",
-  " John Stultz <john.stultz\@linaro.org>",
-  " Todd Kjos <tkjos\@google.com>",
-  " Greg Kroah-Hartman <gregkh\@linuxfoundation.org>",
-  " Christoph Hellwig <hch\@infradead.org>",
-  " Al Viro <viro\@zeniv.linux.org.uk>",
-  " Andrew Morton <akpm\@linux-foundation.org>",
-  " Bruce Fields <bfields\@fieldses.org>",
-  " Jeff Layton <jlayton\@kernel.org>",
-  " Khalid Aziz <khalid.aziz\@oracle.com>",
-  " Lei.Yang\@windriver.com",
-  " linux-fsdevel\@vger.kernel.org",
-  " linux-kselftest\@vger.kernel.org",
-  " Linux-MM <linux-mm\@kvack.org>",
-  " marcandre.lureau\@redhat.com",
-  " Mike Kravetz <mike.kravetz\@oracle.com>",
-  " Minchan Kim <minchan\@kernel.org>",
-  " Shuah Khan <shuah\@kernel.org>",
-  " Valdis Kletnieks <valdis.kletnieks\@vt.edu>",
-  " Hugh Dickins <hughd\@google.com>",
-  " Linux API <linux-api\@vger.kernel.org>\0"
-]
 [
   "\0000:1\0"
 ]
@@ -61,18 +32,18 @@
   "b\0"
 ]
 [
-  "On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel\@joelfernandes.org> wrote:\n",
+  "On Sat, Nov 10, 2018 at 10:24 AM, Joel Fernandes <joel at joelfernandes.org> wrote:\n",
   "> Thanks Andy for your thoughts, my comments below:\n",
   ">\n",
   "> On Fri, Nov 09, 2018 at 10:05:14PM -0800, Andy Lutomirski wrote:\n",
   ">>\n",
   ">>\n",
-  ">> > On Nov 9, 2018, at 7:20 PM, Joel Fernandes <joel\@joelfernandes.org> wrote:\n",
+  ">> > On Nov 9, 2018, at 7:20 PM, Joel Fernandes <joel at joelfernandes.org> wrote:\n",
   ">> >\n",
   ">> >> On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote:\n",
-  ">> >>> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh\@google.com> wrote:\n",
+  ">> >>> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh at google.com> wrote:\n",
   ">> >>> On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google)\n",
-  ">> >>> <joel\@joelfernandes.org> wrote:\n",
+  ">> >>> <joel at joelfernandes.org> wrote:\n",
   ">> >>>> Android uses ashmem for sharing memory regions. We are looking forward\n",
   ">> >>>> to migrating all usecases of ashmem to memfd so that we can possibly\n",
   ">> >>>> remove the ashmem driver in the future from staging while also\n",
@@ -99,13 +70,13 @@
   ">> >>>> The following program shows the seal\n",
   ">> >>>> working in action:\n",
   ">> >>> [...]\n",
-  ">> >>>> Cc: jreck\@google.com\n",
-  ">> >>>> Cc: john.stultz\@linaro.org\n",
-  ">> >>>> Cc: tkjos\@google.com\n",
-  ">> >>>> Cc: gregkh\@linuxfoundation.org\n",
-  ">> >>>> Cc: hch\@infradead.org\n",
-  ">> >>>> Reviewed-by: John Stultz <john.stultz\@linaro.org>\n",
-  ">> >>>> Signed-off-by: Joel Fernandes (Google) <joel\@joelfernandes.org>\n",
+  ">> >>>> Cc: jreck at google.com\n",
+  ">> >>>> Cc: john.stultz at linaro.org\n",
+  ">> >>>> Cc: tkjos at google.com\n",
+  ">> >>>> Cc: gregkh at linuxfoundation.org\n",
+  ">> >>>> Cc: hch at infradead.org\n",
+  ">> >>>> Reviewed-by: John Stultz <john.stultz at linaro.org>\n",
+  ">> >>>> Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n",
   ">> >>>> ---\n",
   ">> >>> [...]\n",
   ">> >>>> diff --git a/mm/memfd.c b/mm/memfd.c\n",
@@ -179,7 +150,7 @@
   ">> > to the new fix? The patch is based on top of this series.\n",
   ">> >\n",
   ">> > ---8<-----------\n",
-  ">> > From: \"Joel Fernandes (Google)\" <joel\@joelfernandes.org>\n",
+  ">> > From: \"Joel Fernandes (Google)\" <joel at joelfernandes.org>\n",
   ">> > Subject: [PATCH] mm/memfd: Fix possible promotion to writeable of sealed memfd\n",
   ">> >\n",
   ">> > Jann Horn found that reopening an F_SEAL_FUTURE_WRITE sealed memfd\n",
@@ -187,8 +158,8 @@
   ">> > without causing ABI breakages and ugly VFS hacks is to simply deny all\n",
   ">> > opens on F_SEAL_FUTURE_WRITE sealed fds.\n",
   ">> >\n",
-  ">> > Reported-by: Jann Horn <jannh\@google.com>\n",
-  ">> > Signed-off-by: Joel Fernandes (Google) <joel\@joelfernandes.org>\n",
+  ">> > Reported-by: Jann Horn <jannh at google.com>\n",
+  ">> > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n",
   ">> > ---\n",
   ">> > mm/shmem.c | 18 ++++++++++++++++++\n",
   ">> > 1 file changed, 18 insertions(+)\n",
@@ -301,4 +272,4 @@
   "--- is there a way to use open_by_handle_at(2) to open a memfd file?"
 ]
 
-05529e5dd692668822080c073c812789c9eb1542d19a58aa1cad4f88993133c4
+4bc334e9a6a9f3c1e73a5215c20ec5260d7eefcbb54fa821832ac00f4fe45fff
