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

diff --git a/a/1.txt b/N1/1.txt
index 120dcf4..9751d3e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,11 +1,11 @@
 On Fri, 2017-07-14 at 11:52 -0700, James Bottomley wrote:
 > On Fri, 2017-07-14 at 14:48 -0400, Mimi Zohar wrote:
-> > The concern is with a shared filesystems.  In that case, for IMA it
-> > would make sense to support a native and a namespace xattr.  If due
+> > The concern is with a shared filesystems. ?In that case, for IMA it
+> > would make sense to support a native and a namespace xattr. ?If due
 > > to xattr space limitations we have to limit the number of xattrs,
 > > then we should limit it to two - a native and a namespace version,
 > > with a "uid=" tag - first namespace gets permission to write the
-> > namespace xattr.  Again, like in the layered case, if the namespace
+> > namespace xattr. ?Again, like in the layered case, if the namespace
 > > xattr doesn't exist, fall back to using the native xattr.
 > 
 > Just on this point: if we're really concerned about the need on shared
@@ -18,12 +18,12 @@ On Fri, 2017-07-14 at 11:52 -0700, James Bottomley wrote:
 > (like NFS) as well as containerised bind mounts.
 
 Writing security.ima requires being root with CAP_SYS_ADMIN
-privileges.  I wouldn't want to give root within the namespace
+privileges. ?I wouldn't want to give root within the namespace
 permission to over write or just extend the native security.ima.
 
 Mimi
 
-_______________________________________________
-Containers mailing list
-Containers@lists.linux-foundation.org
-https://lists.linuxfoundation.org/mailman/listinfo/containers
+--
+To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
+the body of a message to majordomo at vger.kernel.org
+More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index a8de4e3..0da77ce 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -11,31 +11,20 @@
  "ref\020170714173556.GA19669@mail.hallyn.com\0"
  "ref\01500058090.3583.28.camel@linux.vnet.ibm.com\0"
  "ref\01500058362.2853.28.camel@HansenPartnership.com\0"
- "ref\01500058362.2853.28.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org\0"
- "From\0Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>\0"
- "Subject\0Re: [PATCH v2] xattr: Enable security.capability in user namespaces\0"
+ "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0"
+ "Subject\0[PATCH v2] xattr: Enable security.capability in user namespaces\0"
  "Date\0Fri, 14 Jul 2017 16:03:39 -0400\0"
- "To\0James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>"
-  Serge E. Hallyn <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
-  Stefan Berger <stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
- " Mimi Zohar <zohar-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>\0"
- "Cc\0containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  Eric W. Biederman <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
-  casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org
-  Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
- " lkp-JC7UmRfGjtg@public.gmane.org\0"
+ "To\0linux-security-module@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, 2017-07-14 at 11:52 -0700, James Bottomley wrote:\n"
  "> On Fri, 2017-07-14 at 14:48 -0400, Mimi Zohar wrote:\n"
- "> > The concern is with a shared filesystems. \302\240In that case, for IMA it\n"
- "> > would make sense to support a native and a namespace xattr. \302\240If due\n"
+ "> > The concern is with a shared filesystems. ?In that case, for IMA it\n"
+ "> > would make sense to support a native and a namespace xattr. ?If due\n"
  "> > to xattr space limitations we have to limit the number of xattrs,\n"
  "> > then we should limit it to two - a native and a namespace version,\n"
  "> > with a \"uid=\" tag - first namespace gets permission to write the\n"
- "> > namespace xattr. \302\240Again, like in the layered case, if the namespace\n"
+ "> > namespace xattr. ?Again, like in the layered case, if the namespace\n"
  "> > xattr doesn't exist, fall back to using the native xattr.\n"
  "> \n"
  "> Just on this point: if we're really concerned about the need on shared\n"
@@ -48,14 +37,14 @@
  "> (like NFS) as well as containerised bind mounts.\n"
  "\n"
  "Writing security.ima requires being root with CAP_SYS_ADMIN\n"
- "privileges. \302\240I wouldn't want to give root within the namespace\n"
+ "privileges. ?I wouldn't want to give root within the namespace\n"
  "permission to over write or just extend the native security.ima.\n"
  "\n"
  "Mimi\n"
  "\n"
- "_______________________________________________\n"
- "Containers mailing list\n"
- "Containers@lists.linux-foundation.org\n"
- https://lists.linuxfoundation.org/mailman/listinfo/containers
+ "--\n"
+ "To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n"
+ "the body of a message to majordomo at vger.kernel.org\n"
+ More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
-1e166eba0de5de059947503da501ea3213cb547b207bf9dd553549b22d293752
+591a13577bd9fcf3cb800931c7bcc798855ee9192f5495141f559c59d727b444
