[Savannah-cvs] administration/content/gnu-content/faq CVS_-_Ho...

[Michael Clarke]

CVSROOT:        /web/administration
Module name:    administration
Changes by:     Michael Clarke <clarkema>       07/01/26 22:32:12

Modified files:
        content/gnu-content/faq: 
                                 
CVS_-_How_can_I_import_an_existing_repository.txt 
                                 CVS_-_How_can_I_import_my_project.txt 
                                 CVS_-_How_do_I_start_using_the_repository.txt 

Log message:
        Changed the FAQ entries that have just been moved to the wiki to stubs
        pointing to their new wiki location.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/CVS_-_How_can_I_import_an_existing_repository.txt?cvsroot=administration&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/CVS_-_How_can_I_import_my_project.txt?cvsroot=administration&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/CVS_-_How_do_I_start_using_the_repository.txt?cvsroot=administration&r1=1.5&r2=1.6

Patches:
Index: CVS_-_How_can_I_import_an_existing_repository.txt
===================================================================
RCS file: 
/web/administration/administration/content/gnu-content/faq/CVS_-_How_can_I_import_an_existing_repository.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- CVS_-_How_can_I_import_an_existing_repository.txt   13 Apr 2005 21:10:12 
-0000      1.1
+++ CVS_-_How_can_I_import_an_existing_repository.txt   26 Jan 2007 22:32:12 
-0000      1.2
@@ -1,17 +1 @@
-<p>It is possible to import a set of RCS (the file format CVS uses to
-store history) files at Savannah. RCS files usually end with a
-<code>,v</code> extension.</p>
-
-<p>Just open a support request at
-https://savannah.gnu.org/support/?group=administration with an URL for
-the tarball containing your CVS repository. If you do not have an URL
-and the tarball is small, you can attach it to the tracker. Or you can
-say that you cannot provide an URL, and a Savannah hacker will ask you
-to send it by mail.</p>
-
-<p>This is the procedure for importing an existing CVS repository, not
-a set of files. Be sure to send the RCS (<code>,v</code>) files, not a
-tarball of your latest release. To simply import your latest release,
-use the <code>cvs import</code> command.</p>
-
-<p style="font-size: smaller">Updated $Date: 2005/04/13 21:10:12 $</p>
+FAQ moved here: http://savannah.gnu.org/maintenance/CvsImportExistingRepo

Index: CVS_-_How_can_I_import_my_project.txt
===================================================================
RCS file: 
/web/administration/administration/content/gnu-content/faq/CVS_-_How_can_I_import_my_project.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- CVS_-_How_can_I_import_my_project.txt       13 Dec 2005 21:49:14 -0000      
1.2
+++ CVS_-_How_can_I_import_my_project.txt       26 Jan 2007 22:32:12 -0000      
1.3
@@ -1,18 +1 @@
-<p>You should make sure you have access to the repository and make a local
-copy of it, as explained in the first 4 steps of the FAQ entry *How do I Start
-using the CVS repository?*
-</p>
-<p>Once you have a local copy of your empty repository, copy there the whole
-tree for your project and import it to the repository with:</p>
-<pre>
-   cvs add *
-   cvs ci *
-</pre>
-<p>You will get a few warnings about files which should not be committed, 
because this is really a "brute force"
-approach. If you want to avoid those warning messages, you can first add
-directories and then add and commit the files in them. Or use the
-"cvs import" command (its use is a bit more complex for this simple FAQ;
-please read the cvs manual page).
-</p>
-
-<p><font style="font-size: smaller">Update $Date: 2005/12/13 21:49:14 
$</font></p>
+FAQ moved here: http://savannah.gnu.org/maintenance/CvsImportExistingProject

Index: CVS_-_How_do_I_start_using_the_repository.txt
===================================================================
RCS file: 
/web/administration/administration/content/gnu-content/faq/CVS_-_How_do_I_start_using_the_repository.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- CVS_-_How_do_I_start_using_the_repository.txt       4 May 2005 18:50:26 
-0000       1.5
+++ CVS_-_How_do_I_start_using_the_repository.txt       26 Jan 2007 22:32:12 
-0000      1.6
@@ -1,73 +1 @@
-<ol>
-<li>
-First, make sure you have correctly registered in Savannah a SSH for your
-machine, as explained in the FAQ entry *How do I configure my SSH access?*
-</li>
-<li>
-Note that this is only for accessing your repository. To access other
-repositories, use the anonymous mode (check the FAQ entry).
-</li>
-<li>
-<p>Move into the local directory where you want to keep your local copy of the
-CVS tree. For example:</p>
-<pre>
-  mkdir ~/myproj-workingdir
-  cd ~/myproj-workingdir
-</pre>
-</li>
-<li>
-<p>Download the CVS tree structure as explained in your project CVS page (for 
example, https://savannah.gnu.org/cvs/?group=emacs) under &quot;Project 
<i>Member</i> CVS Access via SSH&quot;.
-<p>
-Beware that <b>username</b> and <b>projectname</b> are <i>case sensitive</i>,
-unlike in the web interface.
-<p>
-This will create an empty <i>project</i> directory, where you should start 
writing your project. Ifthere is such no empty directory, check that you are 
not using the <code>-P</code> (prune directory) option in your command line or 
<code>~/.cvsrc</code> file.
-</li>
-<li>
-<p>
-You can now start creating any files you want in your local project directory
-(<code>~/myproj-workingdir/<i>project</i></code> in the example above). Every 
time you create a new file, you must add it and commit it to the repository 
with:
-</p>
-<pre>
-    cvs add filename
-    cvs ci  filename
-</pre>
-<p>You might want to add an -m option to the commit command if you don't want
-to enter an edit session to type a log message:</p>
-<pre>
-    cvs ci -m "your log message" filename
-</pre> 
-<p>When you add a new subdirectory, you just have to add it, not to commit it:
-</p>
-<pre>
-    cvs add dirname
-</pre>
-<p>When you start a new working session, you should first update your
-repository to get any changes done by other developers:</p>
-<pre>
-    cvs update
-</pre>
-<p>And when you modify an existing file, you should commit the changes to the
-repository:</p>
-<pre>
-    cvs ci filename
-</pre>
-</li>
-<li>
-<p>You can see the contents and history of your CVS repository via the ViewCVS 
interface. There are links to this interface in your project page.</p>
-</li>
-</ol>
-
-<p>
-You may want to use a frontend to CVS, we recommend you to try tkcvs, see 
http://www.gnu.org/directory/TkCVS.html
-</p>
-<p>For more info, read
-http://www.freenix.org/unix/linux/HOWTO-vo/CVS-RCS-HOWTO.html
-</p>
-<p>
-You can also read the man page for cvs or the "Quick reference to CVS"
-(http://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_17.html (node
-&quot;Invoking CVS&quot; in the info file)
-</p>
-
-<p style="font-size: smaller">Updated $Date: 2005/05/04 18:50:26 $</p>
+FAQ moved here: http://savannah.gnu.org/maintenance/CvsGettingStarted