|
2200
|
1
|
|
|
2 About CVS write access: by A'rpi
|
|
|
3 ~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
4
|
|
|
5 I. TECH SIDE:
|
|
|
6 =============
|
|
|
7 1. Changing password:
|
|
|
8
|
|
|
9 As you probably got a restricted CVS-only shell, it's not trivial:
|
|
|
10
|
|
|
11 ssh LOGIN@mplayerhq.hu passwd
|
|
|
12
|
|
|
13 (replace LOGIN with your loginname. leave 'passwd' unchanged, it's command)
|
|
|
14
|
|
|
15 Note: if you need real shell for something, tell me.
|
|
|
16
|
|
|
17 2. Checkout devel. source tree:
|
|
|
18
|
|
|
19 export CVS_RSH=ssh
|
|
|
20 cvs -z3 -d:ext:LOGIN@mplayerhq.hu:/cvsroot/mplayer co main
|
|
|
21
|
|
|
22 3. Commiting changes:
|
|
|
23
|
|
|
24 cvs -z3 commit -m "comment - what and why did you change" filename(s)
|
|
|
25
|
|
|
26 4. Adding new files/dirs:
|
|
|
27
|
|
|
28 cvs add filename/dirname
|
|
|
29
|
|
|
30 5. Removing files:
|
|
|
31
|
|
|
32 rm filename
|
|
|
33 cvs remove filename
|
|
|
34
|
|
|
35 6. Check changes:
|
|
|
36
|
|
|
37 cvs -z3 diff -u filename(s)
|
|
|
38
|
|
|
39 7. Check changelog:
|
|
|
40
|
|
|
41 cvs -z3 log filename(s)
|
|
|
42
|
|
|
43 8. Rename/move files:
|
|
|
44
|
|
|
45 you can't do that. ask CVS server admin (A'rpi) to do it.
|
|
|
46 (do not remove & re-add file - it will kill changelog!)
|
|
|
47
|
|
|
48 If you have any tech problems with cvs server, contact me:
|
|
|
49 A'rpi <arpi@thot.banki.hu>
|
|
|
50
|
|
|
51
|
|
|
52 II. POLICY / RULES:
|
|
|
53 ===================
|
|
|
54
|
|
|
55 1. You shouldn't commit code which makes cvs broken!
|
|
|
56 (i mean unfinished but enabled code which break
|
|
|
57 compiling or compiles but does not work)
|
|
|
58
|
|
|
59 2. You don't have over-test things. if it works for you,
|
|
|
60 and you think it should work for others too, then commit.
|
|
|
61 If it has problems (portability, exploits compiler bugs,
|
|
|
62 unusual environment etc) they will be reported, it's ok.
|
|
|
63
|
|
|
64 3. You can commit unfinished stuff (for testing etc), but it
|
|
|
65 must be disabled (#ifdef etc) by default.
|
|
|
66
|
|
|
67 4. Do not change behaviour of the program (renaming options etc)
|
|
|
68 without discussing first at the MPlayer-dev-eng list.
|
|
|
69
|
|
|
70 5. Source indenting and other cosmetical changes are refused.
|
|
|
71 I'll remove those commits...
|
|
|
72 Every developer has its own indenting style, you shouldn't
|
|
|
73 change it. Of course if you (re)write something then you can
|
|
|
74 use your own style...
|
|
|
75 (Many projects forces a given indenting style - we don't)
|
|
|
76
|
|
|
77 6. Always fill out the comment at commiting (-m switch of cvs, or
|
|
|
78 in the editor if you left -m).
|
|
|
79 It shouldn't be such lines: "fixed!" or "Changed it."
|
|
|
80 Describe in a few lines (usually 1 line is enough) what did
|
|
|
81 you changed and why did you that. You can refer mails if bugfix.
|
|
|
82
|
|
|
83 7. If you apply patch by someone else, include his name and email
|
|
|
84 in the cvs comment!
|
|
|
85
|
|
|
86 8. I've developed something called CVS-Backup. It archives CVS
|
|
|
87 repository after each commit - so I can reverse your commits
|
|
|
88 (without messing up changelog) if they are bad.
|
|
|
89
|
|
|
90
|
|
|
91 I think our rules aren't too hard. If you have comments, contact me.
|
