Source string Read only

(itstool) path: sect2/para
Context English State
Policy for Committer Activity in Other Trees
All committers may modify <filename>base/head/share/misc/committers-*.dot</filename>, <filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>, and <filename>ports/head/astro/xearth/files</filename>.
doc committers may commit documentation changes to <filename>src</filename> files, such as man pages, READMEs, fortune databases, calendar files, and comment fixes without approval from a src committer, subject to the normal care and tending of commits.
Any committer may make changes to any other tree with an "Approved by" from a non-mentored committer with the appropriate bit.
Committers can acquire an additional bit by the usual process of finding a mentor who will propose them to core, doceng, or portmgr, as appropriate. When approved, they will be added to 'access' and the normal mentoring period will ensue, which will involve a continuing of <quote>Approved by</quote> for some period.
"Approved by" is only acceptable from non-mentored src committers -- mentored committers can provide a "Reviewed by" but not an "Approved by".
Subversion Primer
New committers are assumed to already be familiar with the basic operation of Subversion. If not, start by reading the <link xlink:href="">Subversion Book</link>.
The FreeBSD source repository switched from <acronym>CVS</acronym> to Subversion on May 31st, 2008. The first real <acronym>SVN</acronym> commit is <emphasis>r179447</emphasis>.
The FreeBSD <literal>doc/www</literal> repository switched from <acronym>CVS</acronym> to Subversion on May 19th, 2012. The first real <acronym>SVN</acronym> commit is <emphasis>r38821</emphasis>.
The FreeBSD <literal>ports</literal> repository switched from <acronym>CVS</acronym> to Subversion on July 14th, 2012. The first real <acronym>SVN</acronym> commit is <emphasis>r300894</emphasis>.
Subversion can be installed from the FreeBSD Ports Collection by issuing these commands:
<prompt>#</prompt> <userinput>pkg install subversion</userinput>
Getting Started
There are a few ways to obtain a working copy of the tree from Subversion. This section will explain them.
Direct Checkout
The first is to check out directly from the main repository. For the <literal>src</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh:// /usr/src</userinput>
For the <literal>doc</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh:// /usr/doc</userinput>
For the <literal>ports</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh:// /usr/ports</userinput>
Though the remaining examples in this document are written with the workflow of working with the <literal>src</literal> tree in mind, the underlying concepts are the same for working with the <literal>doc</literal> and the <literal>ports</literal> tree. Ports related Subversion operations are listed in <xref linkend="ports"/>.
The above command will check out a <literal>CURRENT</literal> source tree as <filename><replaceable>/usr/src/</replaceable></filename>, which can be any target directory on the local filesystem. Omitting the final argument of that command causes the working copy, in this case, to be named <quote>head</quote>, but that can be renamed safely.
<literal>svn+ssh</literal> means the <acronym>SVN</acronym> protocol tunnelled over <acronym>SSH</acronym>. The name of the server is <literal></literal>, <literal>base</literal> is the path to the repository, and <literal>head</literal> is the subdirectory within the repository.
If your FreeBSD login name is different from the login name used on the local machine, either include it in the <acronym>URL</acronym> (for example <literal>svn+ssh://</literal>), or add an entry to <filename>~/.ssh/config</filename> in the form:
User jarjar
This is the simplest method, but it is hard to tell just yet how much load it will place on the repository.
The <command>svn diff</command> does not require access to the server as <acronym>SVN</acronym> stores a reference copy of every file in the working copy. This, however, means that Subversion working copies are very large in size.
<literal>RELENG_*</literal> Branches and General Layout


No matching activity found.

Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/committers-guide.pot, string 97