Even though we don't have currently have active seeds some people still
use the old ones. In addition we may restore creating new ones.
Update the text a bit to reflect that you can use the mirror. Move the
text together into one section, and keep the note about alternatives.
Requested by: kib
There are no such supported branches. Those that need to merge to such
branches can get the information from the documentation archive.
While here, remove an incorrect note that depth cannnot be reduced
(it can be).
We have several lists of important branches. Rather than having to
update them all just mention the important part. Another option might
be to change this to a link with more detailed information.
Perforce no longer provides server binaries for FreeBSD and we haven't
used Perforce for project development in several years.
Reviewed by: bjk (previous version)
Differential Revision: https://reviews.freebsd.org/D15392
I missed this in r51635 when we removed 'All Rights Reserved' from the
preferred license. The phrase is no longer needed and has no legal
meaning now that the Buenos Aires Convention is no longer in force.
Update Bugzilla section of new committer's guide with more detailed
description of Bugzilla account merging and add reference to Kerberos
password generation/change. Based on emails bugmeister@ team receives these
items are the most common sources of confusion for new FeeBSD committers
when it comes to bugtracker.
Reviewed by: mat
Differential Revision: https://reviews.freebsd.org/D12828
% svn copy foo.c bar.c
and
% cp foo.c bar.c
% svn add bar.c
are equivalent. However, the first one keeps foo.c history and the second gets
rid of it.
Fix this and explain the difference.
Reviewed by: brd, allanjude
Approved by: allanjude
Differential Revision: https://reviews.freebsd.org/D12678
Most of those were fixed.
- "(s)" used 5 times Please do not form plurals this way. It is a
holdover from lazy programming practices, is difficult to read, and
almost always unnecessary. A plural formed with a plain "s" is usually
correct when speaking about numbers of one or more.
- "in order to" used 6 times Unless "in order to" has some special
meaning here, "to" is simpler.
- "i.e." used 1 time "I.e." (Latin "id est") means "that is" and is
mostly used in academic and scientific writing. Consider replacing
with the more common English words. Both forms are usually followed by
a comma for a verbal pause: "i.e., a b c" or "that is, a b c"
- "e.g." used 1 time "E.g." (Latin "exempli gratia") means "for example"
and is mostly used in academic and scientific writing. Consider
replacing with the more common English words. Both forms are usually
followed by a comma for a verbal pause: "e.g., a b c" or "for example,
a b c"
- "simply" used 3 times Use "simply" to mean "in a simple manner",
"just", or "merely", not the patronizing "details omitted because they
are not simple enough for you". "basically" used 2 times Use
"basically" to mean "essentially" or "fundamentally", not "only the
basics are shown because anything more will be too complicated for
you".
- "the following" used 18 times "as follows" used 3 times If something
is following, the reader can see it without being told.
- "should" used 83 times Use "should" sparingly, it is feeble and
suggests unsureness. Attempt to be imperative: "do this" rather than
"you should do this".
- "you" used 176 times "your" used 84 times "You" and "your" are
informal and subjective. Attempt to be formal and objective: "the
file" rather than "your file".
Reviewed by: wblock
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7531
There are a couple of different forms of these in use. Add "MFC to:" and
"MFC with:" tags consistent with the existing "MFC after:", and provide
a description so that consistent values can be used.
There are ongoing discussions about "X-MFC-*" tags which still need to be
resolved and documented here, or general guidance on X-MFC-*.
Reviewed by: bcr, ngie
Differential Revision: https://reviews.freebsd.org/D10585
