% 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
As it must be the absolute last line of the commit message, it is better
to put it at the end. Also, add a sentence about that.
Sponsored by: Absolight
It seems that people do not find the exp-run flag when opening a PR.
Reviewed by: bcr, wblock
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7503
can only be located with a secret map that is even more difficult to
locate, requiring the solution of a series of increasingly-obscure
clues... Oh, wait, there it is, right over there.
