Be more specific here about spelling and other trivial or cosmetic changes

to vendor branched files and the repository damage that they cause.  They
are to be strongly avoided.
This commit is contained in:
Peter Wemm 1998-06-10 05:28:59 +00:00
parent 9c96eae1b7
commit 1c28fa4185
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2914

View file

@ -1,4 +1,4 @@
<!-- $Id: policies.sgml,v 1.16 1997-10-19 13:32:12 jraynard Exp $ -->
<!-- $Id: policies.sgml,v 1.17 1998-06-10 05:28:59 peter Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Source Tree Guidelines and Policies
@ -75,6 +75,14 @@ only with the approval of the core team and with the general
consensus of the other developers. The ability to maintain the
package in the future will be a key issue in the decisions.
<p>Please Note: because of some unfortunate design limitations with
the RCS file format and CVS's use of vendor branches, minor, trivial
and/or cosmetic changes are <em>strongly discouraged</em> on files that
are still tracking the vendor branch. "Spelling fixes" are explicitly
included here under the "cosmetic" category and are to be avoided for
files with revision 1.1.x.x. The repository bloat impact from a single
character change can be rather dramatic.
<p>The <tt>Tcl</tt> embedded programming language will be used as example
of how this model works:
@ -105,8 +113,8 @@ and not blunder ahead and hope it "works out". CVS is not forgiving
of import accidents and a fair amount of effort is required to back
out major mistakes.
<p>Because of some unfortunate design limitations with CVS's vendor
branches, it is required that "official" patches from the vendor
<p>Because of the previously mentioned design limitations with CVS's
vendor branches, it is required that "official" patches from the vendor
be applied to the original distributed sources and the result
re-imported onto the vendor branch again. Official patches should
never be patched into the FreeBSD checked out version and