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

Add a bit of back-fill to make the procedures for e.g. GNATS-only

Browse source 
committers more explicit.  This section needs a bit more work.

While here, promote a paragraph to a note, while leaving whitespace alone.
This commit is contained in:
Mark Linimon 2011-02-19 09:34:25 +00:00
parent d8ccca4930
commit df3f30b9ef
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=36950
1 changed files with 7 additions and 2 deletions

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

@ -1052,7 +1052,9 @@ Host pcvs.FreeBSD.org
<title>Conventions and Traditions</title>
<para>As a new developer there are a number of things you should do
first. The first set is specific to committers only.</para>
first. The first set is specific to committers only. (If you are
not a committer, e.g. have GNATS-only access, then your mentor needs
to do these things for you.)</para>
<sect2 id="conventions-committers">
<title>Guidelines For Committers</title>
@ -1142,16 +1144,19 @@ Host pcvs.FreeBSD.org
</listitem>
<listitem>
<para>If you subscribe to &a.svn-src-all.name; or the &a.cvsall;,
<para>(For committers only:)
If you subscribe to &a.svn-src-all.name; or the &a.cvsall;,
you will probably want to unsubscribe to avoid receiving duplicate
copies of commit messages and their followups.</para>
</listitem>
</itemizedlist>
<note>
<para>All <filename>src</filename> commits should go to
&os.current; first before being merged to &os.stable;. No major
new features or high-risk modifications should be made to the
&os.stable; branch.</para>
</note>
</sect2>
<sect2 id="conventions-everyone">