From b6362e9cf5a7cdf4489e44c9e84cc2d085d89dc2 Mon Sep 17 00:00:00 2001 From: Holger Weiss Date: Tue, 19 May 2009 14:18:02 +0200 Subject: Talk about Git instead of CVS Update the Developer Guidelines to reflect the fact that our development is done using Git instead of CVS these days (as noted by Chris Pepper on the "nagiosplug-devel" list). While at it, apply another few minor cleanups. Signed-off-by: Holger Weiss diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 132fada..583f725 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -11,7 +11,7 @@ - 2006 + 2009 Nagios plug-in development guidelines @@ -22,7 +22,7 @@ - 2000 - 2006 + 2000 - 2009 Nagios Plugins Development Team @@ -34,7 +34,7 @@ the plug-in developers and encourage the standarization of the different kind of plug-ins: C, shell, perl, python, etc. - Nagios Plug-in Development Guidelines Copyright (C) 2000-2006 + Nagios Plug-in Development Guidelines Copyright (C) 2000-2009 (Nagios Plugins Team) Permission is granted to make and distribute verbatim @@ -50,18 +50,18 @@ Nagios plugins are developed to the GNU standard, so any OS which is supported by GNU should run the plugins. While the requirements for compiling the Nagios plugins release - is very small, to develop from CVS needs additional software to be installed. These are the - minimum levels of software required: + are very basic, developing from the Git repository requires additional software to be + installed. These are the minimum levels of software required: - gnu make 3.79 - automake 1.9.2 - autoconf 2.59 - gnu m4 1.4.2 - gnu libtool 1.5 + GNU make 3.79 + GNU automake 1.9.2 + GNU autoconf 2.59 + GNU m4 1.4.2 + GNU libtool 1.5 - To compile from CVS, after you have checked out the code, run: + To compile from Git, after you have cloned the repository, run: tools/setup ./configure @@ -748,7 +748,7 @@ setup the tests. Run "make test" to run all the tests. update the THANKS.in file. If you have a change that is useful for noting in the next release, please update the NEWS file. - All CVS commit comments will be written to a ChangeLog at release time. + All commit comments will be written to a ChangeLog at release time. @@ -784,7 +784,7 @@ update the THANKS.in file.
Patches If you have a bug patch, please supply a unified or context diff against the version you are using. For new features, please supply a diff against - the CVS HEAD version. + the Git "master" branch. Patches should be submitted via SourceForge's -- cgit v0.10-9-g596f