Updated csup project description.

Submitted by:	lulf
This commit is contained in:
Robert Watson 2008-03-18 13:17:26 +00:00
parent 609cf2c840
commit 484ec7f42a
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=31685

View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.52 2008/03/18 07:21:30 imp Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.53 2008/03/18 09:26:43 pav Exp $
</cvs:keyword>
</cvs:keywords>
@ -929,19 +929,22 @@ href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html">here</a>.</p>
href="http://mu.org/~mux/csup.html">csup homepage</a>, <a
href="http://www.freebsd.org/cgi/cvsweb.cgi/projects/csup/">CVSweb</a>
</p>
<p>Maxime Henrion is working on a rewrite of CVSup in C, called csup, and he has
imported csup into the FreeBSD base system. It should be ready for use in a
stable environment, but there are however still several missing features.
The following list should be a good starting point:</p>
<p>Maxime Henrion is working on a rewrite of CVSup in C, called csup, and he
has imported csup into the FreeBSD base system. It should be ready for use
in a stable environment, but there are however still several missing
features. The following list should be a good starting point:</p>
<ul>
<li>Add support for authentication.</li>
<li>Add support for shell commands sent by the server.</li>
<li>Add missing support for various CVSup options: -D, -a (requires
authentication support), -e and -E (requires shell commands support)
and the destDir parameter.</li>
<li>Add support for CVS mode. This is important for developers, since this
mode sends the actual RCS files themselves. This is very useful
for storing a full copy of the CVS repository on the client machine.</li>
authentication support), -e and -E (requires shell commands support) and the
destDir parameter.</li>
<li>Add support for CVS mode. This is important for developers, since this
mode sends the actual RCS files themselves. Some parts of this has
already been implemented, such as an RCS parser and an interface to
edit RCS files. The remaining parts for this feature is RCS
correctness testing, protocol correctness testing, fixing bugs and
checking for memory leaks and performance issues.</li>
</ul>
<p><strong>Requirements</strong>:</p>
<ul>