savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [CvsGettingStarted] Moving the FAQ "CVS - How can I impor


From: clarkema
Subject: [Savannah-cvs] [CvsGettingStarted] Moving the FAQ "CVS - How can I import my project" to the wiki
Date: Fri, 26 Jan 2007 21:43:20 +0000

<ol>
<li>
    Firstly, note that this FAQ is concerned only with accessing the
    repositories for projects on which you are a developer.  If you simply want
    to check out code for a project and don't need to commit changes back, you
    should use anonymous access.
</li>
<li>
    Make sure you have correctly registered an SSH key for your machine with
    Savannah, as explained in the FAQ entry *How do I configure my SSH access?*
</li>
<li>
    Move into the local directory where you want to keep your local copy of the
    CVS tree. For example:

    <code>
        mkdir ~/myproj-workingdir
        cd ~/myproj-workingdir
    </code>
</li>
<li>
    <p>
        Download the CVS tree structure as explained in your project's CVS page
        (for example, https://savannah.gnu.org/cvs/?group=emacs) under "Project
        Member CVS Access via SSH".
    </p>

    <p>
        Beware that username and projectname are case sensitive, unlike in the
        web interface.
    </p>

    <p>
        This will create an empty project directory, where you should start
        writing your project. If there is such no empty directory, check that
        you are not using the -P (prune directory) option in your command line
        or ~/.cvsrc file.
    </p>
</li>
<li>
    <p>
        You can now start creating any files you want in your local project
        directory (~/myproj-workingdir/project in the example above). Every
        time you create a new file, you must add it and commit it to the
        repository with:
    </p>
 
    <code>
          cvs add filename
          cvs ci  filename
    </code>

    <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>

    <code>
          cvs ci -m "your log message" filename
    </code>

    <p>
        When you add a new subdirectory, you just have to add it, not to commit
        it:
    </p>

    <code>
          cvs add dirname
    </code>

    <p>
        When you start a new working session, you should first update your
        repository to get any changes made by other developers:
    </p>

    <code>
          cvs update
    </code>

    <p>
        And when you modify an existing file, you should commit the changes to 
the repository:
    </p>

    <code>
          cvs ci filename
    </code>
</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>

    <p>
        You may want to use a frontend to CVS; we recommend tkcvs,
        see <a 
href="http://www.gnu.org/directory/TkCVS.html";>http://www.gnu.org/directory/TkCVS.html</a>
    </p>

    <p>
        For more info, read
        <a 
href="http://www.freenix.org/unix/linux/HOWTO-vo/CVS-RCS-HOWTO.html";>http://www.freenix.org/unix/linux/HOWTO-vo/CVS-RCS-HOWTO.html</a>
    </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
        "Invoking CVS" in the info file) 
    </p>
</li>
</ol>

--
forwarded from 
https://savannah.gnu.org/maintenance/address@hidden://savannah.gnu.org/maintenance




reply via email to

[Prev in Thread] Current Thread [Next in Thread]