From: hal9 Date: Wed, 11 Dec 2002 13:13:32 +0000 (+0000) Subject: Rewrite cvs write access section. X-Git-Tag: v_3_1_archive_branchpoint~47 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=caea99f0ac46b12ada405e96ba719ac64c027faf Rewrite cvs write access section. --- diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 33a73371..bcf2e9f5 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -23,7 +23,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: developer-manual.sgml,v 2.4 2002/09/26 05:57:14 hal9 Exp $ + $Id: developer-manual.sgml,v 2.5 2002/09/26 21:50:39 hal9 Exp $ Copyright (C) 2001, 2002 Privoxy Developers See LICENSE. @@ -48,7 +48,7 @@ - $Id: developer-manual.sgml,v 2.4 2002/09/26 05:57:14 hal9 Exp $ + $Id: developer-manual.sgml,v 2.5 2002/09/26 21:50:39 hal9 Exp $ Quickstart to Privoxy Development + + + The first step is to join the developer's mailing list. + You can submit your ideas, or even better patches. Patches are best + submitted to the Sourceforge tracker set up for this purpose, but + can be sent to the list for review too. + You will also need to have a cvs package installed, which will entail having ssh installed as well (which seems to be a requirement of @@ -146,8 +155,9 @@ Hal. tools is also going to be important (particularly, autoconf and gmake). - For the time being (read, this section is under construction), please - refer to the extensive comments in the source code. + For the time being (read, this section is under construction), you can + also refer to the extensive comments in the source code. In fact, + reading the code is recommended in any case. @@ -155,9 +165,10 @@ Hal. The CVS Repository - If you intend to help us with programming, documentation or packaging - you will need write access to our holy grail, the CVS repository. - Please read this chapter completely before accessing via CVS. + If you become part of the active development team, you will eventually + need write access to our holy grail, the CVS repository. One of the + team members will need to set this up for you. Please read + this chapter completely before accessing via CVS. Access to CVS @@ -1846,7 +1857,7 @@ static void unload_re_filterfile( void *f ) { ... } Example for file comments: -const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 2.4 2002/09/26 05:57:14 hal9 Exp $"; +const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 2.5 2002/09/26 21:50:39 hal9 Exp $"; /********************************************************************* * * File : $Source$ @@ -1906,7 +1917,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.4 2002/09/26 05:57:14 hal9 Exp $" +#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.5 2002/09/26 21:50:39 hal9 Exp $" /********************************************************************* * * File : $Source$ @@ -3018,6 +3029,10 @@ at sourceforge. Three simple steps: Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: developer-manual.sgml,v $ + Revision 2.5 2002/09/26 21:50:39 hal9 + Changes to reflect recent change in stable branch commit policy (hopefully + clearer now). + Revision 2.4 2002/09/26 05:57:14 hal9 Conditionally exclude 'this doc is evolving' comment in intro for non release situations.