Doc : fs : convert xfs.txt to ReST
Quoted 9 lines · Sheriff Esseson
Signed-off-by Sheriff Esseson <sheriffesseson at gmail.com>---
In v3:
UpdateMAINTAINERS. Fix Indentation/long line issues. Insert Sphinx tag.Signature · 1 line
2.22.0
---
In v4:
dax.txt :
fix broken reference to xfs.rst
Documentation/filesystems/dax.txt | 2 +- Documentation/filesystems/index.rst | 5 +- Documentation/filesystems/xfs.rst | 468 +++++++++++++++++++++++++++ Documentation/filesystems/xfs.txt | 470 ---------------------------- MAINTAINERS | 2 +- 5 files changed, 473 insertions(+), 474 deletions(-) create mode 100644 Documentation/filesystems/xfs.rst delete mode 100644 Documentation/filesystems/xfs.txt
Documentation/filesystems/dax.txt +1 -1
@@ -76,7 +76,7 @@ exposure of uninitialized data through mmap. These filesystems may be used for inspiration: - ext2: see Documentation/filesystems/ext2.txt - ext4: see Documentation/filesystems/ext4/ -- xfs: see Documentation/filesystems/xfs.txt +- xfs: see Documentation/filesystems/xfs.rst Handling Media Errors
Documentation/filesystems/index.rst +3 -2
@@ -16,7 +16,7 @@ algorithms work. .. toctree:: :maxdepth: 2 - path-lookup.rst + path-lookup api-summary splice
@@ -40,4 +40,5 @@ Documentation for individual filesystem types can be found here. .. toctree:: :maxdepth: 2 - binderfs.rst + binderfs + xfs
Documentation/filesystems/xfs.rst new file +468 -0
468 lines not on this page · raw message
Documentation/filesystems/xfs.txt deleted +0 -470
470 lines not on this page · raw message
MAINTAINERS +1 -1
@@ -17364,7 +17364,7 @@ L: linux-xfs at vger.kernel.org W: http://xfs.org/ T: git git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git S: Supported -F: Documentation/filesystems/xfs.txt +F: Documentation/filesystems/xfs.rst F: fs/xfs/ XILINX AXI ETHERNET DRIVER
Signature · 1 line
2.22.0
Jonathan Corbet
maintainerQuoted 11 lines · On Sun, 30 Jun 2019 17:50:46 +0100 Sheriff Esseson <sheriffesseson at…
Quoted 9 lines · Sheriff Esseson
Signed-off-by Sheriff Esseson <sheriffesseson at gmail.com>---
In v3:
UpdateMAINTAINERS. Fix Indentation/long line issues. Insert Sphinx tag.Signature · 1 line
2.22.0
Quoted 6 lines
Signed-off-by Sheriff Esseson <sheriffesseson at gmail.com>---
In v4:
dax.txt :
fix broken reference toxfs.rst
I will now repeat what I said yesterday:
Quoted 8 lines
Please do us a favor?
1) Post each patch standalone, without quoted text, ready to be applied.
2) Wait a little while between postings so that you can address more than one comment at a time.
OK, two favors - off-by-one errors are my specialty...:)
I did actually mean that. For "a little while" I meant "a few days or so". Please slow down a little. In any case, we're getting closer to the merge window, so this patch won't be applied for a while regardless.
Thanks,
jon
Quoted 14 lines · Jonathan Corbet
Quoted 11 lines · On Sun, 30 Jun 2019 17:50:46 +0100 Sheriff Esseson <sheriffesseson at…
Quoted 9 lines · Sheriff Esseson
Signed-off-by Sheriff Esseson <sheriffesseson at gmail.com>---
In v3:
UpdateMAINTAINERS. Fix Indentation/long line issues. Insert Sphinx tag.Signature · 1 line
2.22.0
Quoted 12 lines
Quoted 6 lines
Signed-off-by Sheriff Esseson <sheriffesseson at gmail.com>---
In v4:
dax.txt :
fix broken reference toxfs.rstI will now repeat what I said yesterday:
Quoted 3 lines
Please do us a favor?
1) Post each patch standalone, without quoted text, ready to be applied.
To be maybe more explicit,
While we appreciate the eagerness here I'd like to reiterate that the followup V2, V3, ... patches should each be a standalone, self-contained email, without any quoted text and with updated subject lines, i.e.
Subject: [PATCH] Doc : fs : convert xfs.txt to ReST
followed by:
Subject: [PATCH V2] Doc : fs : convert xfs.txt to ReST
followed by:
Subject: [PATCH V3] Doc : fs : convert xfs.txt to ReST
so it's trivial to see from subject lines when a new version has been sent.
Also, what Jonathan said about time between iterations. ;)
Thanks,
-Eric
Quoted 13 lines
Quoted 4 lines
2) Wait a little while between postings so that you can address more than one comment at a time.
OK, two favors - off-by-one errors are my specialty...:)
I did actually mean that. For "a little while" I meant "a few days or so". Please slow down a little. In any case, we're getting closer to the merge window, so this patch won't be applied for a while regardless.
Thanks,
jon