All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <419EA1D7.2060708@yahoo.com.au>

diff --git a/a/content_digest b/N1/content_digest
index 378ace1..dd59d14 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,7 +12,7 @@
  "ref\0Pine.LNX.4.58.0411191726001.1719@schroedinger.engr.sgi.com\0"
  "From\0Nick Piggin <nickpiggin@yahoo.com.au>\0"
  "Subject\0Re: page fault scalability patch V11 [0/7]: overview\0"
- "Date\0Sat, 20 Nov 2004 01:45:59 +0000\0"
+ "Date\0Sat, 20 Nov 2004 12:45:59 +1100\0"
  "To\0Christoph Lameter <clameter@sgi.com>\0"
  "Cc\0Linus Torvalds <torvalds@osdl.org>"
   akpm@osdl.org
@@ -61,4 +61,4 @@
  "be bounded). But if it happened that we really do care anywhere, then the\n"
  write lock should be sufficient.
 
-ccf4ab177be0ccb266b1f69312a4a84202e6b09779a073798cf06d121fcf74b3
+3712f38676c622895d502e657edb0e139ecc3e709c1c538b7ec3c82e159a5094

diff --git a/a/1.txt b/N2/1.txt
index 296eff3..951de5a 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -35,3 +35,8 @@ Yeah the read lock won't do anything to serialise it. I think what Linus
 is saying is that we _don't care_ most of the time (because the error will
 be bounded). But if it happened that we really do care anywhere, then the
 write lock should be sufficient.
+--
+To unsubscribe, send a message with 'unsubscribe linux-mm' in
+the body to majordomo@kvack.org.  For more info on Linux MM,
+see: http://www.linux-mm.org/ .
+Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
diff --git a/a/content_digest b/N2/content_digest
index 378ace1..7689ea5 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -12,7 +12,7 @@
  "ref\0Pine.LNX.4.58.0411191726001.1719@schroedinger.engr.sgi.com\0"
  "From\0Nick Piggin <nickpiggin@yahoo.com.au>\0"
  "Subject\0Re: page fault scalability patch V11 [0/7]: overview\0"
- "Date\0Sat, 20 Nov 2004 01:45:59 +0000\0"
+ "Date\0Sat, 20 Nov 2004 12:45:59 +1100\0"
  "To\0Christoph Lameter <clameter@sgi.com>\0"
  "Cc\0Linus Torvalds <torvalds@osdl.org>"
   akpm@osdl.org
@@ -59,6 +59,11 @@
  "Yeah the read lock won't do anything to serialise it. I think what Linus\n"
  "is saying is that we _don't care_ most of the time (because the error will\n"
  "be bounded). But if it happened that we really do care anywhere, then the\n"
- write lock should be sufficient.
+ "write lock should be sufficient.\n"
+ "--\n"
+ "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
+ "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
+ "see: http://www.linux-mm.org/ .\n"
+ "Don't email: <a href=mailto:\"aart@kvack.org\"> aart@kvack.org </a>"
 
-ccf4ab177be0ccb266b1f69312a4a84202e6b09779a073798cf06d121fcf74b3
+2d0a0a7ad9266f96a617b4bcf68be18ac6bd16304110c4ac5fb5bf37db3b4e79

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.