X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Fintroduction.html;h=1c81cd6062b5a053cfac72d53a8a3addd8275395;hb=52460473669cd31edd8cb8ae66c6b94c489e7e1d;hp=3fe32d281c1d31e7cc04051502e054a5a1f9a9c1;hpb=086d4aacf2fe1d729b4f4a67a7167cb6f19db043;p=privoxy.git diff --git a/doc/webserver/developer-manual/introduction.html b/doc/webserver/developer-manual/introduction.html index 3fe32d28..1c81cd60 100644 --- a/doc/webserver/developer-manual/introduction.html +++ b/doc/webserver/developer-manual/introduction.html @@ -36,11 +36,11 @@

1.1. Quickstart to Privoxy Development

The first step is to join the privoxy-devel 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 git package installed, which will entail having ssh installed as well, in order - to access the git repository. Having the GNU build tools is also going to be important (particularly, autoconf - and gmake).

+ "_top">privoxy-devel mailing list. You can submit your ideas or, even better, patches. Patches can also be + submitted to the Sourceforge patch + tracker.

+

You will also need to have a git package installed, in order to access the git repository. Having the GNU + build tools is also going to be important (particularly, autoconf and gmake).

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.