Page MenuHomeFreeBSD

man: Link mgb.4 to if_mgb.4
ClosedPublic

Authored by otis on Fri, Oct 9, 7:56 PM.
Tags
None
Referenced Files
F175809056: D60551.diff
Tue, Oct 13, 1:12 PM
Unknown Object (File)
Mon, Oct 12, 4:10 AM
Unknown Object (File)
Mon, Oct 12, 2:57 AM
Unknown Object (File)
Mon, Oct 12, 12:44 AM
Unknown Object (File)
Mon, Oct 12, 12:41 AM
Unknown Object (File)
Mon, Oct 12, 12:40 AM
Unknown Object (File)
Mon, Oct 12, 12:34 AM
Unknown Object (File)
Sun, Oct 11, 9:14 PM
Subscribers

Details

Summary

For consistency, create a symbolic link from mgb.4 to also
if_mgb.4

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 77970
Build 74853: arc lint + arc unit

Event Timeline

otis requested review of this revision.Fri, Oct 9, 7:56 PM
This revision is now accepted and ready to land.Fri, Oct 9, 8:13 PM

Thanks for doing this!

This revision was automatically updated to reflect the committed changes.

Create if_mgb.4 symlink on supported architecures only.

If mgb.4 only works on x86, the way to specify that in the manual is to add it to line 25 of mgb.4, like this:

.Dt MGB 4 amd64
share/man/man4/Makefile
799–800

I think you'd actually leave it here, and do it like this, this seems like how the others are done, e.g. bxe.4

957

(except sorted and tabbed and everything)

otis marked 2 inline comments as done.Sat, Oct 10, 6:22 PM
This revision was not accepted when it landed; it landed in state Needs Review.Sat, Oct 10, 9:57 PM
This revision was automatically updated to reflect the committed changes.

There's no reason for mgb to be x86-only

There's no reason for mgb to be x86-only

The manpage matches the kernel module integration, though *shrugs*.

There's no reason for mgb to be x86-only

The manpage matches the kernel module integration, though *shrugs*.

The commit is correct. Documentation needs to match what is actually going on, not what could go on with a trivial rewrite.

However, please please please, if I help you with a commit, use the Discussed with: trailer in accordance with project policy. Because I have to explain what I did each month to pay my bills, but there is too much for me to review/hours I can bill that I do not have time to make a log, I have to just scrape the commit log.

Documentation needs to match what is actually going on, not what could go on with a trivial rewrite.

Yes, of course. Sometimes though it is easier and less work to fix the misbehaviour than to document it -- D60615, which reverts e0a5aa37c1ef3a22e2dc8c311e0e32ea363f7ccf and 2d935a1e93af4d552db1f7218ef97e01f058c084.