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

Corrected links to CVS info at cyclic.com, various grammar and typo fixes.

Browse source 
Also reworded in a couple places for clarity's sake.
This commit is contained in:
Daniel Harris 2000-07-08 15:32:00 +00:00
parent 45aed53b93
commit 6312bd2fb1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7534
2 changed files with 16 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$Date: 2000-06-08 18:12:54 $</pubdate>
<pubdate>$Date: 2000-07-08 15:32:00 $</pubdate>
<copyright>
<year>1999</year>
@ -32,7 +32,7 @@
operations on the FreeBSD central repository machine. A basic
familiarity with CVS is already assumed, although CVS
reference information, tutorials, and FAQs can also be found
at: <ulink url="http://www.cyclic.com/cyclic-pages/books.html">http://www.cyclic.com/cyclic-pages/books.html</ulink></para>
at: <ulink url="http://www.cyclic.com/CVS/support">http://www.cyclic.com/CVS/support</ulink></para>
<para>Good luck, and welcome aboard!</para>
</abstract>
@ -150,7 +150,7 @@
<title>Conventions and Traditions</title>
<para>The CVS Repository Meisters (Peter Wemm and John Polstra)
are the <quote>owners</quote> of the CVS repository and
are the <quote>owners</quote> of the CVS repository and are
responsible for any and <emphasis>all</emphasis> direct
modification of it for the purposes of cleanup or fixing some
grievous abuse of CVS by a committer. No one else should
@ -243,8 +243,8 @@
proprietary interest in the area affected, go ahead and commit
it.</para>
<para>If you are at all unsure about a commit for any reason in
general, have it reviewed by <literal>-hackers</literal> first
<para>If you are unsure about a commit for any reason at
all, have it reviewed by <literal>-hackers</literal>
before committing. Better to have it flamed then and there
rather than when it is part of the CVS repository. If you do
happen to commit something which results in controversy
@ -291,7 +291,7 @@
<para>You can run a local copy of GNATS, and then integrate the FreeBSD
GNATS tree in to it using CVSup. Then you can run GNATS commands
locally, or us other interfaces, such as <command>tkgnats</command>.
locally, or use other interfaces, such as <command>tkgnats</command>.
This lets you query the PR database without needing to be connected to
the Internet.</para>
@ -317,7 +317,7 @@
<programlisting>gnats/[a-ce-z]*</programlisting>
<para>The rest of this examples assume you have only supped the
<para>The rest of these examples assume you have only supped the
<literal>docs</literal> category. Adjust them as necessary,
depending on the categories you are synching.</para>
</step>
@ -938,7 +938,7 @@ docs:Documentation Bug:nik:</programlisting>
<para>Do not mix style fixes with new functionality. A style
fix is any change which does not modify the functionality of
the code. Mixing the changes ofucsates the functionality
the code. Mixing the changes obfuscates the functionality
change when using <command>cvs diff</command>, which can hide
any new bugs. Do not include whitespace changes with content
changes in commits to <filename>doc/</filename> or

16
en_US.ISO_8859-1/articles/committers-guide/article.sgml
View file

@ -16,7 +16,7 @@
</author>
</authorgroup>
<pubdate>$Date: 2000-06-08 18:12:54 $</pubdate>
<pubdate>$Date: 2000-07-08 15:32:00 $</pubdate>
<copyright>
<year>1999</year>
@ -32,7 +32,7 @@
operations on the FreeBSD central repository machine. A basic
familiarity with CVS is already assumed, although CVS
reference information, tutorials, and FAQs can also be found
at: <ulink url="http://www.cyclic.com/cyclic-pages/books.html">http://www.cyclic.com/cyclic-pages/books.html</ulink></para>
at: <ulink url="http://www.cyclic.com/CVS/support">http://www.cyclic.com/CVS/support</ulink></para>
<para>Good luck, and welcome aboard!</para>
</abstract>
@ -150,7 +150,7 @@
<title>Conventions and Traditions</title>
<para>The CVS Repository Meisters (Peter Wemm and John Polstra)
are the <quote>owners</quote> of the CVS repository and
are the <quote>owners</quote> of the CVS repository and are
responsible for any and <emphasis>all</emphasis> direct
modification of it for the purposes of cleanup or fixing some
grievous abuse of CVS by a committer. No one else should
@ -243,8 +243,8 @@
proprietary interest in the area affected, go ahead and commit
it.</para>
<para>If you are at all unsure about a commit for any reason in
general, have it reviewed by <literal>-hackers</literal> first
<para>If you are unsure about a commit for any reason at
all, have it reviewed by <literal>-hackers</literal>
before committing. Better to have it flamed then and there
rather than when it is part of the CVS repository. If you do
happen to commit something which results in controversy
@ -291,7 +291,7 @@
<para>You can run a local copy of GNATS, and then integrate the FreeBSD
GNATS tree in to it using CVSup. Then you can run GNATS commands
locally, or us other interfaces, such as <command>tkgnats</command>.
locally, or use other interfaces, such as <command>tkgnats</command>.
This lets you query the PR database without needing to be connected to
the Internet.</para>
@ -317,7 +317,7 @@
<programlisting>gnats/[a-ce-z]*</programlisting>
<para>The rest of this examples assume you have only supped the
<para>The rest of these examples assume you have only supped the
<literal>docs</literal> category. Adjust them as necessary,
depending on the categories you are synching.</para>
</step>
@ -938,7 +938,7 @@ docs:Documentation Bug:nik:</programlisting>
<para>Do not mix style fixes with new functionality. A style
fix is any change which does not modify the functionality of
the code. Mixing the changes ofucsates the functionality
the code. Mixing the changes obfuscates the functionality
change when using <command>cvs diff</command>, which can hide
any new bugs. Do not include whitespace changes with content
changes in commits to <filename>doc/</filename> or