All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20200306004555.GB225345@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index f39184f..2f8542d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -51,3 +51,9 @@ Is this behavior intentional at all?  It seems like a bug; it seems the inode
 should be written just once, during the sync.  
 
 - Eric
+
+
+_______________________________________________
+Linux-f2fs-devel mailing list
+Linux-f2fs-devel@lists.sourceforge.net
+https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
diff --git a/a/content_digest b/N1/content_digest
index 7d89236..e7865c4 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,5 +1,5 @@
  "From\0Eric Biggers <ebiggers@kernel.org>\0"
- "Subject\0lazytime causing inodes to remain dirty after sync?\0"
+ "Subject\0[f2fs-dev] lazytime causing inodes to remain dirty after sync?\0"
  "Date\0Thu, 5 Mar 2020 16:45:55 -0800\0"
  "To\0linux-fsdevel@vger.kernel.org\0"
  "Cc\0linux-ext4@vger.kernel.org"
@@ -58,6 +58,12 @@
  "Is this behavior intentional at all?  It seems like a bug; it seems the inode\n"
  "should be written just once, during the sync.  \n"
  "\n"
- - Eric
+ "- Eric\n"
+ "\n"
+ "\n"
+ "_______________________________________________\n"
+ "Linux-f2fs-devel mailing list\n"
+ "Linux-f2fs-devel@lists.sourceforge.net\n"
+ https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
 
-c11d2d58f6256d3cc9e8ade06c49d61f0221ce87eb67125090fb478c7bb15acc
+774eca257c9ad1cc9ab51cf0c2175db863fe1f32ab5959010595a0d868a55cd9

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.