diff for duplicates of <1521645586.3848.136.camel@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index b08533a..fba4b37 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -21,32 +21,27 @@ On Thu, 2018-03-15 at 15:35 -0500, Eric W. Biederman wrote:
 > solutions that don't work as well.
 
 IMA-measurement and IMA-audit need to be enabled from the very
-beginning.  The only reason we differentiate between IMA-measurement
+beginning.  The only reason we differentiate between IMA-measurement
 and IMA-audit from IMA-appraisal is simply because the initramfs
-doesn't include xattrs.  Once support for CPIO xattrs is upstreamed,
-IMA-appraisal could then also be enabled from the very beginning.  For
+doesn't include xattrs.  Once support for CPIO xattrs is upstreamed,
+IMA-appraisal could then also be enabled from the very beginning.  For
 now, we rely on the initramfs being measured (and appraised) and
 enable IMA-appraisal before any files are accessed from real root.
- Systems with a custom /init today already can enable IMA-appraisal
-from the very beginning.  
+ Systems with a custom /init today already can enable IMA-appraisal
+from the very beginning.  
 
 In terms of IMA namespacing, we shouldn't need to differentiate
-between IMA-measurement and IMA-audit from IMA-appraisal.  All of them
+between IMA-measurement and IMA-audit from IMA-appraisal.  All of them
 should be initialized from the very beginning to capture all
 measurements in the measurement list, audit the measurements and
 appraise all files.
 
 Requiring IMA namespacing to be joined to another namespace
 complicates things, like the unnecessary creation of IMA namespaces.
- Just as there is an "owning" namespace for other namespaces, there
+ Just as there is an "owning" namespace for other namespaces, there
 should be an "owning" IMA namespace, which is independent of either
 the mount or user namespace.
 
 (I hope I'm using the term "owning" properly here.)
 
 Mimi
-
-_______________________________________________
-Containers mailing list
-Containers@lists.linux-foundation.org
-https://lists.linuxfoundation.org/mailman/listinfo/containers
diff --git a/a/content_digest b/N1/content_digest
index 2516547..9366db2 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -11,21 +11,20 @@
  "ref\087sh915eo0.fsf@xmission.com\0"
  "ref\019ecc296-b584-4e1a-5369-30090fbc7880@linux.vnet.ibm.com\0"
  "ref\087d10513id.fsf@xmission.com\0"
- "ref\087d10513id.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org\0"
- "From\0Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>\0"
+ "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0"
  "Subject\0Re: [RFC PATCH v2 1/3] ima: extend clone() with IMA namespace support\0"
  "Date\0Wed, 21 Mar 2018 11:19:46 -0400\0"
- "To\0Eric W. Biederman <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>"
- " Stefan Berger <stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>\0"
- "Cc\0mkayaalp-4hyTIkVWTs8LubxHQvXPfYdd74u8MsAO@public.gmane.org"
-  Mehmet Kayaalp <mkayaalp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
-  sunyuqiong1988-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
-  containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  david.safford-JJi787mZWgc@public.gmane.org
-  James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
-  linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
- " linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0"
+ "To\0Eric W. Biederman <ebiederm@xmission.com>"
+ " Stefan Berger <stefanb@linux.vnet.ibm.com>\0"
+ "Cc\0James Bottomley <James.Bottomley@hansenpartnership.com>"
+  mkayaalp@cs.binghamton.edu
+  Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>
+  sunyuqiong1988@gmail.com
+  containers@lists.linux-foundation.org
+  linux-kernel@vger.kernel.org
+  david.safford@ge.com
+  linux-security-module@vger.kernel.org
+ " linux-integrity@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Thu, 2018-03-15 at 15:35 -0500, Eric W. Biederman wrote:\n"
@@ -51,34 +50,29 @@
  "> solutions that don't work as well.\n"
  "\n"
  "IMA-measurement and IMA-audit need to be enabled from the very\n"
- "beginning. \302\240The only reason we differentiate between IMA-measurement\n"
+ "beginning.  The only reason we differentiate between IMA-measurement\n"
  "and IMA-audit from IMA-appraisal is simply because the initramfs\n"
- "doesn't include xattrs. \302\240Once support for CPIO xattrs is upstreamed,\n"
- "IMA-appraisal could then also be enabled from the very beginning. \302\240For\n"
+ "doesn't include xattrs.  Once support for CPIO xattrs is upstreamed,\n"
+ "IMA-appraisal could then also be enabled from the very beginning.  For\n"
  "now, we rely on the initramfs being measured (and appraised) and\n"
  "enable IMA-appraisal before any files are accessed from real root.\n"
- "\302\240Systems with a custom /init today already can enable IMA-appraisal\n"
- "from the very beginning. \302\240\n"
+ " Systems with a custom /init today already can enable IMA-appraisal\n"
+ "from the very beginning.  \n"
  "\n"
  "In terms of IMA namespacing, we shouldn't need to differentiate\n"
- "between IMA-measurement and IMA-audit from IMA-appraisal. \302\240All of them\n"
+ "between IMA-measurement and IMA-audit from IMA-appraisal.  All of them\n"
  "should be initialized from the very beginning to capture all\n"
  "measurements in the measurement list, audit the measurements and\n"
  "appraise all files.\n"
  "\n"
  "Requiring IMA namespacing to be joined to another namespace\n"
  "complicates things, like the unnecessary creation of IMA namespaces.\n"
- "\302\240Just as there is an \"owning\" namespace for other namespaces, there\n"
+ " Just as there is an \"owning\" namespace for other namespaces, there\n"
  "should be an \"owning\" IMA namespace, which is independent of either\n"
  "the mount or user namespace.\n"
  "\n"
  "(I hope I'm using the term \"owning\" properly here.)\n"
  "\n"
- "Mimi\n"
- "\n"
- "_______________________________________________\n"
- "Containers mailing list\n"
- "Containers@lists.linux-foundation.org\n"
- https://lists.linuxfoundation.org/mailman/listinfo/containers
+ Mimi
 
-ef5e6abab41f302f260a6502e905cafc18320e03e57543e808c25ba699388a45
+0ffe136eb27742ed21c13e644c1680ccb21206ced1f5844f107b21817676b257
