diff for duplicates of <20110629065306.GC1026@dastard>

diff --git a/a/1.txt b/N1/1.txt
index 1d4bb15..2772326 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,8 +1,6 @@
 On Tue, Jun 28, 2011 at 11:33:19AM -0400, Josef Bacik wrote:
-> This is a test to make sure seek_data/seek_hole is acting like it doe=
-s on
-> Solaris.  It will check to see if the fs supports finding a hole or n=
-ot and will
+> This is a test to make sure seek_data/seek_hole is acting like it does on
+> Solaris.  It will check to see if the fs supports finding a hole or not and will
 > adjust as necessary.
 
 So I just looked at this with an eye to validating an XFS
@@ -33,7 +31,7 @@ does not cover that I'd need to test in some way:
 	  writes close together in a file, and XFS is also known to
 	  fill holes when doing sparse writes past EOF.
 
-	- only tests single block data extents =D1=95o doesn't cover
+	- only tests single block data extents ѕo doesn't cover
 	  corner cases like skipping over multiple fragmented data
 	  extents to the next hole.
 
@@ -54,8 +52,8 @@ Some more comments in line....
 > +_supported_fs generic
 > +_supported_os Linux
 > +
-> +testfile=3D$TEST_DIR/seek_test.$$
-> +logfile=3D$TEST_DIR/seek_test.$$.log
+> +testfile=$TEST_DIR/seek_test.$$
+> +logfile=$TEST_DIR/seek_test.$$.log
 
 The log file is usually named $seq.full, and doesn't get placed in
 the filesystem being tested. It gets saved in the xfstests directory
@@ -87,7 +85,7 @@ to run the test manually and see what it is doing easily...
 > +rm -f $logfile
 > +rm -f $testfile
 > +
-> +status=3D0 ; exit
+> +status=0 ; exit
 > diff --git a/255.out b/255.out
 > new file mode 100644
 > index 0000000..7eefb82
@@ -117,7 +115,7 @@ Otherwise, the test code looks ok if a bit over-engineered....
 > +	char	*test_desc;
 > +};
 > +
-> +struct testrec seek_tests[] =3D {
+> +struct testrec seek_tests[] = {
 > +	{  1, test01, "Test basic support" },
 > +	{  2, test02, "Test an empty file" },
 > +	{  3, test03, "Test a full file" },
@@ -156,11 +154,11 @@ Cheers,
 
 Dave.
 
---=20
+-- 
 Dave Chinner
 david@fromorbit.com
---
-To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
-in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
+
+_______________________________________________
+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 1baae93..7957e19 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,17 +5,15 @@
  "Date\0Wed, 29 Jun 2011 16:53:07 +1000\0"
  "To\0Josef Bacik <josef@redhat.com>\0"
  "Cc\0linux-fsdevel@vger.kernel.org"
+  viro@zeniv.linux.org.uk
   linux-kernel@vger.kernel.org
   linux-btrfs@vger.kernel.org
-  xfs@oss.sgi.com
- " viro@zeniv.linux.org.uk\0"
+ " xfs@oss.sgi.com\0"
  "\00:1\0"
  "b\0"
  "On Tue, Jun 28, 2011 at 11:33:19AM -0400, Josef Bacik wrote:\n"
- "> This is a test to make sure seek_data/seek_hole is acting like it doe=\n"
- "s on\n"
- "> Solaris.  It will check to see if the fs supports finding a hole or n=\n"
- "ot and will\n"
+ "> This is a test to make sure seek_data/seek_hole is acting like it does on\n"
+ "> Solaris.  It will check to see if the fs supports finding a hole or not and will\n"
  "> adjust as necessary.\n"
  "\n"
  "So I just looked at this with an eye to validating an XFS\n"
@@ -46,7 +44,7 @@
  "\t  writes close together in a file, and XFS is also known to\n"
  "\t  fill holes when doing sparse writes past EOF.\n"
  "\n"
- "\t- only tests single block data extents =D1=95o doesn't cover\n"
+ "\t- only tests single block data extents \321\225o doesn't cover\n"
  "\t  corner cases like skipping over multiple fragmented data\n"
  "\t  extents to the next hole.\n"
  "\n"
@@ -67,8 +65,8 @@
  "> +_supported_fs generic\n"
  "> +_supported_os Linux\n"
  "> +\n"
- "> +testfile=3D$TEST_DIR/seek_test.$$\n"
- "> +logfile=3D$TEST_DIR/seek_test.$$.log\n"
+ "> +testfile=$TEST_DIR/seek_test.$$\n"
+ "> +logfile=$TEST_DIR/seek_test.$$.log\n"
  "\n"
  "The log file is usually named $seq.full, and doesn't get placed in\n"
  "the filesystem being tested. It gets saved in the xfstests directory\n"
@@ -100,7 +98,7 @@
  "> +rm -f $logfile\n"
  "> +rm -f $testfile\n"
  "> +\n"
- "> +status=3D0 ; exit\n"
+ "> +status=0 ; exit\n"
  "> diff --git a/255.out b/255.out\n"
  "> new file mode 100644\n"
  "> index 0000000..7eefb82\n"
@@ -130,7 +128,7 @@
  "> +\tchar\t*test_desc;\n"
  "> +};\n"
  "> +\n"
- "> +struct testrec seek_tests[] =3D {\n"
+ "> +struct testrec seek_tests[] = {\n"
  "> +\t{  1, test01, \"Test basic support\" },\n"
  "> +\t{  2, test02, \"Test an empty file\" },\n"
  "> +\t{  3, test03, \"Test a full file\" },\n"
@@ -169,13 +167,13 @@
  "\n"
  "Dave.\n"
  "\n"
- "--=20\n"
+ "-- \n"
  "Dave Chinner\n"
  "david@fromorbit.com\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-btrfs\" =\n"
- "in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ "\n"
+ "_______________________________________________\n"
+ "xfs mailing list\n"
+ "xfs@oss.sgi.com\n"
+ http://oss.sgi.com/mailman/listinfo/xfs
 
-9b1cf2403d3059ae68d49bc3470e1b86993573acf740ebf59942dd1b574f289b
+23cee8152ff0075a5466aa3872e2b469f4409ea5effbefdaefe5b0369cf962a5
