4 >The CVS Repository</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy Developer Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Documentation Guidelines"
17 HREF="documentation.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy Developer Manual</TH
47 HREF="introduction.html"
60 HREF="documentation.html"
74 >2. The CVS Repository</A
77 > If you intend to help us with programming, documentation or packaging
78 you will need write access to our holy grail, the CVS repository.
79 Please read this chapter completely before accessing via CVS.
87 >2.1. Access to CVS</A
90 > The project's CVS repository is hosted on
92 HREF="http://sourceforge.net/"
96 Please refer to the chapters 6 and 7 in
98 HREF="http://sourceforge.net/docman/?group_id=1"
102 > for the technical access details for your
103 operating system. For historical reasons, the CVS server is
106 >cvs.ijbswa.sourceforge.net</TT
111 >, and the source tree module is called
124 >2.2. CVS Commit Guideline</A
127 > The source tree is the heart of every software project. Every effort must
128 be made to ensure that it is readable, compilable and consistent at all
129 times. We therefore ask anyone with CVS access to strictly adhere to the
130 following guidelines:
139 >) be tempted to commit
140 that small change without testing it thoroughly first. When we're
141 close to a public release, ask a fellow developer to review your
147 > Your commit message should give a concise overview of <I
151 > (no big details) and <I
153 >why you changed it</I
155 Just check previous messages for good examples.
160 > Don't use the same message on multiple files, unless it equally applies to
166 > If your changes span multiple files, and the code won't recompile unless
167 all changes are commited (e.g. when changing the signature of a function),
168 then commit all files one after another, without long delays in beween.
169 If necessary, prepare the commit messages in advance.
174 > Before changing things on CVS, make sure that your changes are in line
175 with the team's general consensus on what should be done (see below).
188 >2.3. Discussing Changes First</A
191 > We don't have a too formal policy on this, just use common sense. Hints: If it is..
198 > ..a bugfix / clean-up / cosmetic thing: shoot
203 > ..a new feature that can be turned off: shoot
208 > ..a clear improvement w/o side effects on other parts of the code: shoot
213 > ..a matter of taste: <A
214 HREF="mailto:developers@privoxy.org"
222 > ..a major redesign of some part of the code: <A
223 HREF="mailto:developers@privoxy.org"
234 > Note that near a major public release, we get a bit more cautious - if
235 unsure, it doesn't hurt to ask first. There is always the possibility
236 to submit a patch to the <A
237 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
260 HREF="introduction.html"
276 HREF="documentation.html"
295 >Documentation Guidelines</TD