Page MenuHomeFreeBSD

netgraph/ng_pipe: Add missing man page
ClosedPublic

Authored by donner on Oct 17 2019, 4:39 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 4, 4:07 AM
Unknown Object (File)
Jan 20 2024, 11:28 PM
Unknown Object (File)
Dec 22 2023, 9:48 PM
Unknown Object (File)
Nov 15 2023, 8:57 AM
Unknown Object (File)
Nov 9 2023, 3:16 PM
Unknown Object (File)
Nov 8 2023, 10:12 PM
Unknown Object (File)
Nov 8 2023, 10:34 AM
Unknown Object (File)
Nov 8 2023, 10:06 AM

Details

Reviewers
brueffer
Group Reviewers
manpages
Commits
rS353780: Add a manpage for ng_pipe(4).
Summary

There is no man page for the netgraph node ng_pipe.
This is my attempt to add one.

Test Plan
man 4 ng_pipe

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 27100
Build 25379: arc lint + arc unit

Event Timeline

Thank you for the man page.

Can you run textproc/igor and "mandoc -Tlint" over your man page? They will display some warnings and provide some hint on which line they are.
We also have a bit of info here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/manpages-markup.html

share/man/man4/ng_pipe.4
67

You need to have a line break after a sentence stop.

77

Another (two actually) line break here.

82

Line break after the sentence stop.

86

A line break after the sentence stop is needed here, too.

Fixed "mandoc -Tlint" issues. Thank you for the hint.

brueffer added a subscriber: brueffer.
brueffer added inline comments.
share/man/man4/ng_pipe.4
75

superfluous "the"

81

Superfluous comma

87

much -> many

103

though -> through

111

"to the one specified in"

215

Stray comma

This revision now requires changes to proceed.Oct 18 2019, 9:34 AM
donner marked 6 inline comments as done.

Fixing spelling and more as pointed out by brueffer.

This revision is now accepted and ready to land.Oct 18 2019, 10:57 AM

Please remember to hook it up to the man4 Makefile.

Added Makefile reference in order to allow installing the man page.

This revision now requires review to proceed.Oct 18 2019, 11:20 AM

Please commit, if you have rights.

One last question, is the copyright correct? If you just used a different manpage as a template but you wrote all the content, you should be the sole copyright holder here.

One last question, is the copyright correct? If you just used a different manpage as a template but you wrote all the content, you should be the sole copyright holder here.

Interesting question. I believe the copyright belongs to the code, not to the documentation.
Therefore I copied this from the source.

Code and manpage are separate copyrightable items. I suppose the code examples could justify the existing copyrights, but you should definitely add yourself as copyright holder as well.

Added copyright for the man page author

Update local working directory on my machine.

This revision was not accepted when it landed; it landed in state Needs Review.Oct 20 2019, 8:58 PM
This revision was automatically updated to reflect the committed changes.