From 0402e26824111f395e760601649c7741baf7979e Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Fri, 7 May 2010 06:33:09 +0000 Subject: [PATCH] Mark "RCS" as an acronym and add a 'role' attribute wit its expansion This may help a bit when people are not familiar with the specific meaning of RCS we are alluding to in the dev handbook. Triggered by: A discussion with other doc-people and Walt Pawley, walt at wump.org. --- .../books/developers-handbook/policies/chapter.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml index c474d3a233..7b48da3e25 100644 --- a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml @@ -131,7 +131,7 @@ key issue in the decisions. - Because of some unfortunate design limitations with the RCS file + Because of some unfortunate design limitations with the RCS file format and the use of vendor branches, minor, trivial and/or cosmetic changes are strongly discouraged on files that are still tracking the vendor branch. Spelling @@ -167,7 +167,7 @@ The important thing here is that the src/contrib/file directory is created according to the rules: it is supposed to contain the sources as distributed (on a - proper vendor-branch and without RCS keyword expansion) with as few + proper vendor-branch and without RCS keyword expansion) with as few FreeBSD-specific changes as possible. If there are any doubts on how to go about it, it is imperative that you ask first and not blunder ahead and hope it works out.