Page MenuHomeFreeBSD

Improve svn copy documentation
ClosedPublic

Authored by romain on Oct 15 2017, 5:15 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 28 2023, 6:32 PM
Unknown Object (File)
Dec 20 2023, 2:19 AM
Unknown Object (File)
Nov 28 2023, 9:12 AM
Unknown Object (File)
Nov 7 2023, 1:15 AM
Unknown Object (File)
Nov 4 2023, 4:15 PM
Unknown Object (File)
Nov 3 2023, 9:01 PM
Unknown Object (File)
Nov 1 2023, 10:02 AM
Unknown Object (File)
Oct 6 2023, 12:10 AM
Subscribers

Details

Summary

The documentation incorrectly states that

% 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, which is the reason why we do repocopies.

Fix this and explain the difference.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Added @wblock as a reviewer because he did the commit that introduced this ambiguity :-)

Typo fix.

en_US.ISO8859-1/articles/committers-guide/article.xml
968 ↗(On Diff #34000)

s/usualy/usually/

romain marked an inline comment as done.

Fix typo

This revision is now accepted and ready to land.Oct 17 2017, 2:27 PM
This revision was automatically updated to reflect the committed changes.
head/en_US.ISO8859-1/articles/committers-guide/article.xml
968

This sentence long and has a lot of information. Better to split.

Also, best to avoid possessives, which are rarely needed.

Suggested:

Using <command>svn copy</command> is usually preferable because it
keeps the history of the original file with the new file.  When the original file is manually
copied to a new file, then added to version control, the new file does not have the
commit history of the original.