William Hubbs posted on Fri, 30 Jan 2015 16:22:38 -0600 as excerpted: > this is covered in the nfs-utils-1.3.1-r1 ebuild by ewarns; however, qa > asked me to write a news item as well, so here it is. > > Let me know what you think. > > Thanks, > > William > > Title: nfsmount service renamed nfsclient > Author: William Hubbs <willi...@gentoo.org> > Content-Type: text/plain > Posted: 2015-02-02 > Revision: 2
Repeating a comment I've seen for other news items: The Revision header is intended for machine-parsing use AFTER original release, in case an earlier release needed corrected and thus a revision other than 1. As such, it should always be Revision: 1 when first released, and thus for all pre-release review postings, unless there has actually been a previous release and the review posting is actually reviewing a correction-revision of a previously released news item found to be in actual need of revision after release. For those familiar with the news and mail header RFCs, think of the Revision header value greater than one as a Supersedes. If the original was never released, there's nothing to supersede, and revision should always be 1. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
