diff for duplicates of <20190628053320.GA26902@lst.de> diff --git a/a/1.txt b/N1/1.txt index ab231b0..b20798c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -45,7 +45,7 @@ in every copy of the XFS code that would otherwise show up. > problems that we had with the existing IO path, and we'll go back to > implementing our own writeback path.... ->From the high level POV I agree with your stance. But the point is +From the high level POV I agree with your stance. But the point is that the writeback code is not tightly integrated with xfs, and that is why I don't want it in XFS. It is on other other hand very tightly integrated with the iomap buffer read and write into pagecache diff --git a/a/content_digest b/N1/content_digest index d45a8a7..d0b5d3d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -63,7 +63,7 @@ "> problems that we had with the existing IO path, and we'll go back to\n" "> implementing our own writeback path....\n" "\n" - ">From the high level POV I agree with your stance. But the point is\n" + "From the high level POV I agree with your stance. But the point is\n" "that the writeback code is not tightly integrated with xfs, and that\n" "is why I don't want it in XFS. It is on other other hand very\n" "tightly integrated with the iomap buffer read and write into pagecache\n" @@ -82,4 +82,4 @@ "scheme all the details stay 100% in XFS in the split code, as the\n" abstraction between iomap and xfs is very clear and allows for that. -650a1da6b8930be151b056ea57d233a593143007431367163c2b1da9e8932395 +22d4e24e3aa5768f5cdd1c8da3f4a3f100dad83fd83cc20fbe5fd095a278a4c8
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.