modules/versioncontrol_cvs/README.txt

$Id: README.txt,v 1.3 2007/08/21 17:28:46 jpetso Exp $

CVS backend for Version Control API -
Provides CVS commit information and account management as a pluggable backend.


SHORT DESCRIPTION
-----------------
This module provides an implementation of the Version Control API that makes
it possible to use the CVS version control system. It can retrieve commit
information by parsing commit logs or by using the xcvs-* trigger scripts
that are called directly by CVS when a commit or tag operation is executed.

For the API documentation, have a look at the module file or run doxygen/phpdoc
on it to get a fancier version of the docs.

Any bug reports or feature requests concerning the xcvs-* scripts or
the CVS backend in general should be submitted to the CVS backend issue queue:
http://drupal.org/project/issues/versioncontrol_cvs

If you know that the functionality is (or should be) provided by the
Version Control API (and not by the CVS backend), please submit an issue there:
http://drupal.org/project/issues/versioncontrol


AUTHOR
------
Jakob Petsovits <jpetso at gmx DOT at>


CREDITS
-------
A good amount of code in Version Control / Project Node Integration was taken
from the CVS integration module on drupal.org, its authors (Kjartan Mannes and
Derek Wright, among others) deserve a lot of credits and may also hold
copyright for parts of this module.

This module was originally created as part of Google Summer of Code 2007,
so Google deserves some credits for making this possible. Thanks also
to Derek Wright (dww) and Andy Kirkham (AjK) for mentoring
the Summer of Code project.
1	$Id: README.txt,v 1.3 2007/08/21 17:28:46 jpetso Exp $
2
3	CVS backend for Version Control API -
4	Provides CVS commit information and account management as a pluggable backend.
5
6
7	SHORT DESCRIPTION
8	-----------------
9	This module provides an implementation of the Version Control API that makes
10	it possible to use the CVS version control system. It can retrieve commit
11	information by parsing commit logs or by using the xcvs-* trigger scripts
12	that are called directly by CVS when a commit or tag operation is executed.
13
14	For the API documentation, have a look at the module file or run doxygen/phpdoc
15	on it to get a fancier version of the docs.
16
17	Any bug reports or feature requests concerning the xcvs-* scripts or
18	the CVS backend in general should be submitted to the CVS backend issue queue:
19	http://drupal.org/project/issues/versioncontrol_cvs
20
21	If you know that the functionality is (or should be) provided by the
22	Version Control API (and not by the CVS backend), please submit an issue there:
23	http://drupal.org/project/issues/versioncontrol
24
25
26	AUTHOR
27	------
28	Jakob Petsovits <jpetso at gmx DOT at>
29
30
31	CREDITS
32	-------
33	A good amount of code in Version Control / Project Node Integration was taken
34	from the CVS integration module on drupal.org, its authors (Kjartan Mannes and
35	Derek Wright, among others) deserve a lot of credits and may also hold
36	copyright for parts of this module.
37
38	This module was originally created as part of Google Summer of Code 2007,
39	so Google deserves some credits for making this possible. Thanks also
40	to Derek Wright (dww) and Andy Kirkham (AjK) for mentoring
41	the Summer of Code project.