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

Add "What is a repo-copy" Q&A, I've seen it asked a few times...

Browse source
This commit is contained in:
Ben Smithurst 2000-07-11 21:36:22 +00:00
parent 5c2711290f
commit a95aa3e58e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7567
2 changed files with 44 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.68 2000/07/11 15:40:26 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.69 2000/07/11 15:42:14 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -8761,6 +8761,27 @@ back when.</para>
</answer></qandaentry>
<qandaentry><question>
<para>What is a repo-copy?</para></question><answer>
<para>A repo-copy (which is a short form of &ldquo;repository
copy&rdquo;) refers to the direct copying of files within the CVS
repository.</para>
<para>Without a repo-copy, if a file needed to be copied or moved to
another place in the repository, the committer would run <command>cvs
add</command> to put the file in its new location, and then <command>cvs
rm</command> on the old file if the old copy was being removed.</para>
<para>The disadvantage of this method is that the history (i.e. the
entries in the CVS logs) of the file would not be copied to the new
location. As the FreeBSD Project considers this history very useful,
a repository copy is often used instead. This is a process where one
of the repository meisters will copy the files directly within the
repository, rather than using the <command>cvs</command> program.</para>
</answer></qandaentry>
<qandaentry><question>
<para>How many FreeBSD hackers does it take to change a lightbulb?</para></question><answer>

23
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.68 2000/07/11 15:40:26 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.69 2000/07/11 15:42:14 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -8761,6 +8761,27 @@ back when.</para>
</answer></qandaentry>
<qandaentry><question>
<para>What is a repo-copy?</para></question><answer>
<para>A repo-copy (which is a short form of &ldquo;repository
copy&rdquo;) refers to the direct copying of files within the CVS
repository.</para>
<para>Without a repo-copy, if a file needed to be copied or moved to
another place in the repository, the committer would run <command>cvs
add</command> to put the file in its new location, and then <command>cvs
rm</command> on the old file if the old copy was being removed.</para>
<para>The disadvantage of this method is that the history (i.e. the
entries in the CVS logs) of the file would not be copied to the new
location. As the FreeBSD Project considers this history very useful,
a repository copy is often used instead. This is a process where one
of the repository meisters will copy the files directly within the
repository, rather than using the <command>cvs</command> program.</para>
</answer></qandaentry>
<qandaentry><question>
<para>How many FreeBSD hackers does it take to change a lightbulb?</para></question><answer>