os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Mark "RCS" as an acronym and add a 'role' attribute wit its expansion

Browse source 
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.
This commit is contained in:
Giorgos Keramidas 2010-05-07 06:33:09 +00:00
parent 08c69888fd
commit 0402e26824
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=35715
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
View file

@ -131,7 +131,7 @@
key issue in the decisions.</para> key issue in the decisions.</para>
<note> <note>
<para>Because of some unfortunate design limitations with the RCS file <para>Because of some unfortunate design limitations with the <acronym role="Revision Control System">RCS</acronym> file
format and the use of vendor branches, minor, trivial and/or format and the use of vendor branches, minor, trivial and/or
cosmetic changes are <emphasis>strongly discouraged</emphasis> on cosmetic changes are <emphasis>strongly discouraged</emphasis> on
files that are still tracking the vendor branch. <quote>Spelling files that are still tracking the vendor branch. <quote>Spelling
@ -167,7 +167,7 @@
<para>The important thing here is that the <para>The important thing here is that the
<filename>src/contrib/file</filename> directory is created according to <filename>src/contrib/file</filename> directory is created according to
the rules: it is supposed to contain the sources as distributed (on a 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 <acronym>RCS</acronym> keyword expansion) with as few
FreeBSD-specific changes as possible. If there are any doubts on 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 how to go about it, it is imperative that you ask first and not blunder
ahead and hope it <quote>works out</quote>.</para> ahead and hope it <quote>works out</quote>.</para>