diff for duplicates of <20180530101003.GA31419@lst.de> diff --git a/a/1.txt b/N1/1.txt index 5991d6f..9188e2a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote: -> In that case,? maybe it would be simpler to drop it for GFS2. Unless we +> In that case, maybe it would be simpler to drop it for GFS2. Unless we > are getting a lot of benefit from it, then we should probably just follow > the generic pattern here. Eventually we'll move everything to iomap, so > that the bh mapping interface will be gone. That implies that we might be diff --git a/a/content_digest b/N1/content_digest index 1b07f50..02306cf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,13 +5,20 @@ "ref\020180530095911.GB31068@lst.de\0" "ref\0e14b3cfb-73ca-e712-e1e9-4ceabc8c7b6d@redhat.com\0" "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0[Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to\tgfs2\0" + "Subject\0Re: [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2\0" "Date\0Wed, 30 May 2018 12:10:03 +0200\0" - "To\0cluster-devel.redhat.com\0" + "To\0Steven Whitehouse <swhiteho@redhat.com>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Darrick J. Wong <darrick.wong@oracle.com> + linux-xfs@vger.kernel.org + linux-fsdevel@vger.kernel.org + cluster-devel@redhat.com + linux-mm@kvack.org + " Andreas Gr\303\274nbacher <agruenba@redhat.com>\0" "\00:1\0" "b\0" "On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote:\n" - "> In that case,? maybe it would be simpler to drop it for GFS2. Unless we \n" + "> In that case,\302\240 maybe it would be simpler to drop it for GFS2. Unless we \n" "> are getting a lot of benefit from it, then we should probably just follow \n" "> the generic pattern here. Eventually we'll move everything to iomap, so \n" "> that the bh mapping interface will be gone. That implies that we might be \n" @@ -23,4 +30,4 @@ "does for SSDs, and it probably doesn't do a useful thing for modern\n" disks with intelligent caches either. -000ac845a33567d032bd80f5633aafe016e0b59f4f4e8cbca4f5d659b8de474b +64477af181246ca3ab1e8dc03d262f837327265063af2b5f7cf533a083617ca7
diff --git a/a/1.txt b/N2/1.txt index 5991d6f..26f3156 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote: -> In that case,? maybe it would be simpler to drop it for GFS2. Unless we +> In that case,� maybe it would be simpler to drop it for GFS2. Unless we > are getting a lot of benefit from it, then we should probably just follow > the generic pattern here. Eventually we'll move everything to iomap, so > that the bh mapping interface will be gone. That implies that we might be diff --git a/a/content_digest b/N2/content_digest index 1b07f50..09b0419 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -5,13 +5,20 @@ "ref\020180530095911.GB31068@lst.de\0" "ref\0e14b3cfb-73ca-e712-e1e9-4ceabc8c7b6d@redhat.com\0" "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0[Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to\tgfs2\0" + "Subject\0Re: [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2\0" "Date\0Wed, 30 May 2018 12:10:03 +0200\0" - "To\0cluster-devel.redhat.com\0" + "To\0Steven Whitehouse <swhiteho@redhat.com>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Darrick J. Wong <darrick.wong@oracle.com> + linux-xfs@vger.kernel.org + linux-fsdevel@vger.kernel.org + cluster-devel@redhat.com + linux-mm@kvack.org + " Andreas Gr\303\274nbacher <agruenba@redhat.com>\0" "\00:1\0" "b\0" "On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote:\n" - "> In that case,? maybe it would be simpler to drop it for GFS2. Unless we \n" + "> In that case,\303\257\302\277\302\275 maybe it would be simpler to drop it for GFS2. Unless we \n" "> are getting a lot of benefit from it, then we should probably just follow \n" "> the generic pattern here. Eventually we'll move everything to iomap, so \n" "> that the bh mapping interface will be gone. That implies that we might be \n" @@ -23,4 +30,4 @@ "does for SSDs, and it probably doesn't do a useful thing for modern\n" disks with intelligent caches either. -000ac845a33567d032bd80f5633aafe016e0b59f4f4e8cbca4f5d659b8de474b +7662af792569ee5b72d24461eccd4f13738e50810528c66e6e7be41b4721ed84
diff --git a/a/1.txt b/N3/1.txt index 5991d6f..e9afaf2 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,5 +1,5 @@ On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote: -> In that case,? maybe it would be simpler to drop it for GFS2. Unless we +> In that case, maybe it would be simpler to drop it for GFS2. Unless we > are getting a lot of benefit from it, then we should probably just follow > the generic pattern here. Eventually we'll move everything to iomap, so > that the bh mapping interface will be gone. That implies that we might be diff --git a/a/content_digest b/N3/content_digest index 1b07f50..e9b2c16 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -5,13 +5,20 @@ "ref\020180530095911.GB31068@lst.de\0" "ref\0e14b3cfb-73ca-e712-e1e9-4ceabc8c7b6d@redhat.com\0" "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0[Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to\tgfs2\0" + "Subject\0Re: [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2\0" "Date\0Wed, 30 May 2018 12:10:03 +0200\0" - "To\0cluster-devel.redhat.com\0" + "To\0Steven Whitehouse <swhiteho@redhat.com>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Darrick J. Wong <darrick.wong@oracle.com> + linux-xfs@vger.kernel.org + linux-fsdevel@vger.kernel.org + cluster-devel@redhat.com + linux-mm@kvack.org + " Andreas Gr\303\274nbacher <agruenba@redhat.com>\0" "\00:1\0" "b\0" "On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote:\n" - "> In that case,? maybe it would be simpler to drop it for GFS2. Unless we \n" + "> In that case, maybe it would be simpler to drop it for GFS2. Unless we \n" "> are getting a lot of benefit from it, then we should probably just follow \n" "> the generic pattern here. Eventually we'll move everything to iomap, so \n" "> that the bh mapping interface will be gone. That implies that we might be \n" @@ -23,4 +30,4 @@ "does for SSDs, and it probably doesn't do a useful thing for modern\n" disks with intelligent caches either. -000ac845a33567d032bd80f5633aafe016e0b59f4f4e8cbca4f5d659b8de474b +04548f3087edf3431bdb49fae9d2ab040dcdfa5069c93339d20b5fad13837501
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.