diff for duplicates of <200901310248.42820.arnd@arndb.de>

diff --git a/a/1.txt b/N1/1.txt
index cfd74fd..2e59ad4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,5 +1,5 @@
 On Saturday 31 January 2009, Andrew Morton wrote:
-> Is this written in a standard somewhere?  Is it guaranteed?
+> Is this written in a standard somewhere? ?Is it guaranteed?
 
 Alignment is defined in the architecture psABI documents. 
 Unfortunately, many of them were written before the 'long long'
@@ -13,7 +13,7 @@ issues with 16/32 bit integers, but those don't apply here.
 
 > If some (perhaps non-gcc) compiler were to lay this out differently
 > (perhaps with suitable command-line options) then that's liveable
-> with - as long as the kernel never changes the layout.  Of course
+> with - as long as the kernel never changes the layout. ?Of course
 > it would be better to avoid this if poss.
 
 If a compiler was using irregular structure alignment, all sorts of
@@ -37,8 +37,3 @@ There is also no leak of uninitialized data here, because this structure
 is only read, never written.
 
 	Arnd <><
-
-_______________________________________________
-xfs mailing list
-xfs@oss.sgi.com
-http://oss.sgi.com/mailman/listinfo/xfs
diff --git a/a/content_digest b/N1/content_digest
index 1342861..75baea3 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,23 +2,23 @@
  "ref\0200901310138.34164.arnd@arndb.de\0"
  "ref\020090130171423.f99c88d0.akpm@linux-foundation.org\0"
  "From\0Arnd Bergmann <arnd@arndb.de>\0"
- "Subject\0Re: [PATCH] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls\0"
- "Date\0Sat, 31 Jan 2009 02:48:41 +0100\0"
+ "Subject\0[Ocfs2-devel] [PATCH] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls\0"
+ "Date\0Sat, 31 Jan 2009 01:49:17 -0000\0"
  "To\0Andrew Morton <akpm@linux-foundation.org>\0"
- "Cc\0mfasheh@suse.com"
+ "Cc\0Ankit Jain <me@ankitjain.org>"
+  viro@zeniv.linux.org.uk
+  hch@infradead.org
+  linux-fsdevel@vger.kernel.org
+  mfasheh@suse.com
   joel.becker@oracle.com
+  ocfs2-devel@oss.oracle.com
   linux-kernel@vger.kernel.org
-  hch@infradead.org
   xfs-masters@oss.sgi.com
-  viro@zeniv.linux.org.uk
-  Ankit Jain <me@ankitjain.org>
-  linux-fsdevel@vger.kernel.org
-  xfs@oss.sgi.com
- " ocfs2-devel@oss.oracle.com\0"
+ " xfs@oss.sgi.com\0"
  "\00:1\0"
  "b\0"
  "On Saturday 31 January 2009, Andrew Morton wrote:\n"
- "> Is this written in a standard somewhere? \302\240Is it guaranteed?\n"
+ "> Is this written in a standard somewhere? ?Is it guaranteed?\n"
  "\n"
  "Alignment is defined in the architecture psABI documents. \n"
  "Unfortunately, many of them were written before the 'long long'\n"
@@ -32,7 +32,7 @@
  "\n"
  "> If some (perhaps non-gcc) compiler were to lay this out differently\n"
  "> (perhaps with suitable command-line options) then that's liveable\n"
- "> with - as long as the kernel never changes the layout. \302\240Of course\n"
+ "> with - as long as the kernel never changes the layout. ?Of course\n"
  "> it would be better to avoid this if poss.\n"
  "\n"
  "If a compiler was using irregular structure alignment, all sorts of\n"
@@ -55,11 +55,6 @@
  "There is also no leak of uninitialized data here, because this structure\n"
  "is only read, never written.\n"
  "\n"
- "\tArnd <><\n"
- "\n"
- "_______________________________________________\n"
- "xfs mailing list\n"
- "xfs@oss.sgi.com\n"
- http://oss.sgi.com/mailman/listinfo/xfs
+ "\tArnd <><"
 
-d5f5982f589b05a1977bccd4c31c3c4d5e50b9c93a54afb6de641f6ab008f175
+0b4059011751bee2287d19aa5094347311c3e725fd3433e929931fee75688931
