summaryrefslogtreecommitdiff
path: root/external/bsd/am-utils/dist/cvs-server.txt
blob: a2a123eb7e2d5ed513ce7d73ad9be84b9f7988c3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
##############################################################################
Here are generic CVS server instructions:

(1) Get an SSH Public key installed on cvs.am-utils.org.  You can generate a
    public/private key pair using ssh-keygen(1).  Then copy the key into
    your ~/.ssh/authorized_keys file on cvs.am-utils.org.  If you don't have
    login access on cvs.am-utils.org, then email
    am-utils-developers@am-utils.org.

(2) Then, check out a fresh copy of 6.2 (development branch)

$ export CVS_RSH=ssh
$ cvs -d ${USER}@cvs.am-utils.org:/home/cvsroot checkout am-utils

    Or, to checkout the stable branch:

$ cvs -d ${USER}@cvs.am-utils.org:/home/cvsroot checkout -r amd-6-1-stable am-utils

    Or, to checkout the legacy branch:

$ cvs -d ${USER}@cvs.am-utils.org:/home/cvsroot checkout -r amd-6-0-stable am-utils

(3) Then you can do normal edit, commit, update, etc. without having to
    worry about your $CVSROOT or the -d option.  Just remember to keep
    setting CVS_RSH=ssh in your environment (or put it in your
    .profile/.login file).

##############################################################################
To merge changes from the stable branch into the main (development) branch:

$ cvs update -j amd-6-1-stable -kk

- don't worry about all the files that change; it's probably because of cvs
  keywords in the sources

- after the merge, do a 'cvs update -d' and resolve any conflicts

Nevertheless, please exercise caution when merging branches.

##############################################################################