Bug 209429

Summary: Possible typo in FreeBSD 10.3-RELEASE Release Notes
Product: Documentation Reporter: sweeney
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed Overcome By Events    
Severity: Affects Some People CC: bjk
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
URL: https://www.freebsd.org/releases/10.3R/relnotes.html

Description sweeney 2016-05-10 15:35:10 UTC 
In Section:

10. Networking

The line:

"A bug in the epair(4) virtual Ethernet interface which could cause a panic when running ifconfig(8) create and destory quickly has been fixed. [r287594]"

Should probably read 'destroy' rather than 'destory'.

Utterly trivial, I know, but if someone is in that area anyway it should only take seconds to fix.

Tony.
Comment 1 sweeney 2016-05-11 01:03:34 UTC 
I'm a software build engineer by profession, so if someone could point me at a URL to check out the source and submit a patch, I'd be happy to do so.

Tony.
Comment 2 Benjamin Kaduk freebsd_committer freebsd_triage 2016-05-12 03:55:26 UTC 
The source file for that document may be viewed at https://svnweb.freebsd.org/base/releng/10.3/release/doc/en_US.ISO8859-1/relnotes/article.xml?revision=297257&view=markup and lives in Subversion.  Unfortunately, it is in the base/releng part of the tree, which means that (1) only the release engineers are authorized to modify it and (2) it is unlikely to be touched, since the release is already final.

So, while we appreciate the report, I think that WONTFIX is the best resolution we can come up with given the current system.  (Hmm, bugzilla doesn't have that status. "overcome by events", since the release is final, I guess.)
Comment 3 sweeney 2016-05-13 12:35:05 UTC 
It's hard to argue with that.  My personal take as a release engineer is that even though the code is final, blatant documentation errata could and should be fixed in line, since of necessity they become final after the remainder of the software.  In this case it doesn't matter, since the text is merely descriptive. But if the text were intended to be cut and pasted then it would merit a post hoc fix, in my view.