All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <aeHkdon2GH8UUkE4@infradead.org>

diff --git a/a/1.txt b/N1/1.txt
index 5274288..a06dfe7 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -23,3 +23,10 @@ _has_metadata_journaling check, which also needed further btrfs
 workarounds.  AFAICS it is all about failing the mount if log recovery
 is required, but the underlying block device is read-only.  So maybe
 name it after that?
+
+
+
+_______________________________________________
+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 dd85f7b..b6aa6f5 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,7 +2,7 @@
  "ref\0ad3zThMKaWZ65XE2@infradead.org\0"
  "ref\0aeER8AIJZecuTLIc@zlang-mailbox\0"
  "From\0Christoph Hellwig <hch@infradead.org>\0"
- "Subject\0Re: [PATCH] generic/050: handle f2fs as nojournal filesystem\0"
+ "Subject\0Re: [f2fs-dev] [PATCH] generic/050: handle f2fs as nojournal filesystem\0"
  "Date\0Fri, 17 Apr 2026 00:42:46 -0700\0"
  "To\0Christoph Hellwig <hch@infradead.org>"
   Jan Prusakowski <jprusakowski@google.com>
@@ -37,6 +37,13 @@
  "_has_metadata_journaling check, which also needed further btrfs\n"
  "workarounds.  AFAICS it is all about failing the mount if log recovery\n"
  "is required, but the underlying block device is read-only.  So maybe\n"
- name it after that?
+ "name it after that?\n"
+ "\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
 
-56b7e1b747962bf98300beddaf557ec4df3bd3f45e2408c98339154a3661eda9
+2bdbe6751aa1f074975e0ffa22cc60e9199c6c6f1fb96bbbeafaeeab42c6e444

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.