Add a SEE ALSO
section to the manpages.
Master:
This PR:
Should be enough to close #29558.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For detailed information about the code coverage, see the test coverage report.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | jarolrod, willcl-ark, pablomartin4btc, laanwj |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
tACK 7c3ac598dd9a1f1a506c4931249ff6c9f1c949ba
master
pr
ACK 7c3ac598dd9a1f1a506c4931249ff6c9f1c949ba
I don’t see it as a big issue to list all related binaries in the bitcoin “ecosystem” in the SEE ALSO section myself.
61@@ -62,6 +62,10 @@
62 # Copyright is the same for all binaries, so just use the first.
63 footer.write('[COPYRIGHT]\n')
64 footer.write('\n'.join(versions[0][2]).strip())
65+ # Create SEE ALSO section
66+ footer.write('\n[SEE ALSO]\n')
67+ footer.write(', '.join(s.rpartition('/')[2] + '(1)' for s in BINARIES))
Could use os.path.basename
it’s slightly more readable and will always pick the last path item.
Edit: wait, so does rpartition
, confused it for normal split
. It’s fine like this.