-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8344056: Use markdown format for man pages #22081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Welcome back ihse! A progress list of the required criteria for merging this PR into |
@magicus This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 84 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@magicus The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Without looking in detail at the changes, this is indeed a welcome and long-overdue change! |
Webrevs
|
I think this means the one-true-master copy of a man page is now the public .md file. |
So glad to see progress here!
should read If only one could suggest changes in files not touched by a pull request: https://github.com/orgs/community/discussions/9099 |
Yes, related: Also related: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to finally see this happen!
Just one glitch with the GPL headers.
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A missing .1
to .md
file extension change in javadoc
's manpage self-test CheckManPageOptions.java
is causing the CI to fail.
Details in #22081 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The jwebserver.md looks OK to me.
Now |
sigh
Let me have a look at it first. It seems the test has the indention to handle markdown files, so maybe there is an easy fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating all the licenses to GPL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I'm somewhat surprised that the full src tree is available to this test when it runs. I was expecting it to examine the .1 files in the JDK image. |
The CheckManPageOptions test had regexps that were not up to date with the latest changes in the markdown file. I fixed those and now the test passes. |
It's been like that since the test was created in https://bugs.openjdk.org/browse/JDK-8274211, so there is no change in this PR. |
/integrate |
Going to push as commit 475feb0.
Your commit was automatically rebased without conflicts. |
Is the warning log when pandoc is not installed a bit loud?
|
@eirbjo Yes, that was not intentional. https://bugs.openjdk.org/browse/JDK-8344559. |
Currently, the man pages are stored as troff (a text format) in the open repo, and a content-wise identical copy is stored as markdown (another text format) in the closed repo.
Since markdown is preferred to troff in terms of editing, we make changes to the man pages in markdown and then convert it to troff.
This closed-markdown to open-troff processing needs to be done manually by an Oracle engineer. This is done regularly at the start and end of a new release cycle, adding to the burden of creating a new release. It is also done (if any of the reviewers knows about the process) whenever an Oracle engineer updates a man page. If a community contributor changes the behavior of a tool, an Oracle engineer needs to change the documentation for them, since they cannot do it themselves.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22081/head:pull/22081
$ git checkout pull/22081
Update a local copy of the PR:
$ git checkout pull/22081
$ git pull https://git.openjdk.org/jdk.git pull/22081/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22081
View PR using the GUI difftool:
$ git pr show -t 22081
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22081.diff
Using Webrev
Link to Webrev Comment