diff for duplicates of <20260817070240.GA17371@lst.de> diff --git a/a/1.txt b/N1/1.txt index 9004680..4c7dd11 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -20,3 +20,10 @@ dust for the current merges settles. I can have the lazy bounce series ready early for the merge window, and should be able to send it out once all depdendency trees hit mainline. Does that sound good? Or should we split the minimum requirements into a separate branch? + + + +_______________________________________________ +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 95992b8..a0ed348 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,23 +1,23 @@ "ref\020260814092448.1818082-1-aalbersh@kernel.org\0" "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0Re: [PATCH v15 00/25] fs-verity support for XFS with post EOF merkle tree\0" + "Subject\0Re: [f2fs-dev] [PATCH v15 00/25] fs-verity support for XFS with post EOF merkle tree\0" "Date\0Mon, 17 Aug 2026 09:02:40 +0200\0" "To\0Andrey Albershteyn <aalbersh@kernel.org>\0" - "Cc\0djwong@kernel.org" - ebiggers@kernel.org - hch@lst.de + "Cc\0fsverity@lists.linux.dev" Jens Axboe <axboe@kernel.dk> + linux-ext4@vger.kernel.org + djwong@kernel.org Carlos Maiolino <cem@kernel.org> - fsverity@lists.linux.dev - linux-fsdevel@vger.kernel.org - linux-xfs@vger.kernel.org + david@fromorbit.com linux-unionfs@vger.kernel.org - linux-block@vger.kernel.org - linux-ext4@vger.kernel.org linux-f2fs-devel@lists.sourceforge.net - linux-btrfs@vger.kernel.org - david@fromorbit.com - " Tal Zussman <tz2294@columbia.edu>\0" + ebiggers@kernel.org + linux-block@vger.kernel.org + linux-fsdevel@vger.kernel.org + Tal Zussman <tz2294@columbia.edu> + linux-xfs@vger.kernel.org + hch@lst.de + " linux-btrfs@vger.kernel.org\0" "\00:1\0" "b\0" "On Fri, Aug 14, 2026 at 11:24:17AM +0200, Andrey Albershteyn wrote:\n" @@ -41,6 +41,13 @@ "dust for the current merges settles. I can have the lazy bounce series\n" "ready early for the merge window, and should be able to send it out\n" "once all depdendency trees hit mainline. Does that sound good? Or\n" - should we split the minimum requirements into a separate branch? + "should we split the minimum requirements into a separate branch?\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 -56147193fece8e6dbd6309447012babd72a0035d6165177de7d06a9d4c076466 +accc407c23aa00e1ead865464a61df28e7003312ffed7e6c59a53f3f1cb26ef2
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.