Revision: 51815
http://brlcad.svn.sourceforge.net/brlcad/?rev=51815&view=rev
Author: carlmoore
Date: 2012-08-08 15:35:27 +0000 (Wed, 08 Aug 2012)
Log Message:
-----------
fix spellings
Modified Paths:
--------------
brlcad/trunk/doc/cvs.txt
Modified: brlcad/trunk/doc/cvs.txt
===================================================================
--- brlcad/trunk/doc/cvs.txt 2012-08-08 15:21:02 UTC (rev 51814)
+++ brlcad/trunk/doc/cvs.txt 2012-08-08 15:35:27 UTC (rev 51815)
@@ -43,7 +43,7 @@
for correct and proper functionality.
4. Commit and update frequently. Large or complicated changes should
- be broken up into smaller succint commits as best possible to make
+ be broken up into smaller succinct commits as best possible to make
reviewing easier. Commit working code early and commit often.
5. Be consistent and informative. Tags need to follow a consistent
@@ -99,7 +99,7 @@
The intent of this document is to cover the broad aspects of how
CVS is to be organized and used. This includes branch management,
tag naming conventions, checking sources in and out, and other
- relevent usage policy.
+ relevant usage policy.
CVS branches should be used to separate out the various types of
source code revisions. These include:
@@ -116,7 +116,7 @@
maintenance branch may and should exist for making patch releases.
Finally, various experimental and developer undertakings that may
benefit by being isolated from changes to HEAD or STABLE, or would
- likewise be distruptive to normal HEAD functionality, may live on
+ likewise be disruptive to normal HEAD functionality, may live on
a branch of their own.
It's very important that the main CVS HEAD revision be a "mostly"
@@ -153,7 +153,7 @@
will checkout using the default implicit :ext: method and will
need to provide an authorized username. Be sure to use the "-P"
checkout option to remove (prune) empty directories. The "-z9"
- global CVS option is encouraged to minimze network utilization.
+ global CVS option is encouraged to minimize network utilization.
FROM HEAD:
@@ -457,7 +457,7 @@
FORMAT FOR MISCELLANEOUS TAGS:
For everything else, the basic structure of the tags still
- applies. Lower case, dash-separated, and hopefully succintly
+ applies. Lower case, dash-separated, and hopefully succinctly
informative tag names should be used. Dates are highly
recommended as CVS tags are not associated by date, but rather
to the individual revision of a file.
@@ -530,7 +530,7 @@
In this example, brlcad is an unmodified top-level source
directory and "brlcad.modified" is a top-level source directory
that has been modified. That same patch file may then be applied
- to a checkout and commited to CVS.
+ to a checkout and committed to CVS.
If there is an active maintenance branch that a patch was started
from, it is generally easier to apply the patch to the maintenance
@@ -589,7 +589,7 @@
The comment should contain or be the keyword of the branch being
merged in. For example, "premerge-20040315-windows" indicates a
- merge that occured on March 15th, 2004, from the windows-branch.
+ merge that occurred on March 15th, 2004, from the windows-branch.
If there are any conflicts, they would of course need to be
manually resolved. Once any conflicts are resolved and the
@@ -717,7 +717,7 @@
way to cope. If you still REALLY need to move a directory, a
little find scripting can make it easy. In case you didn't get
the hint DO NOT MOVE/RENAME DIRECTORIES unless there's a _very_
- good reason. This implictly means that extra care and thought
+ good reason. This implicitly means that extra care and thought
should be made when naming new directories to be added to the
repository.
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BRL-CAD Source Commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-commits
