cvs commit: doc/en_US.ISO8859-1/books/handbook/cutting-edge chapter.sgml

Doug Barton dougb at
Wed Jul 7 17:43:18 UTC 2010

On 7/7/2010 9:42 AM, Johann Kois wrote:
> If I remember correctly cvsup does some things csup can not do.
> Handling a local cvsup repository, for example.

If you're going to update the documentation it's kind of important that
you know these kinds of facts first. :)  For some time now csup has been
a drop-in replacement for all of the client functions of cvsup. The only
thing it doesn't have is a GUI.

> If we do not mention cvsup here anymore than we would need to get rid of
> cvsup in the whole chapter AND in the "Using CVSup" chapter of the
> handbook.

I posted something about this to -doc a little while ago suggesting that
the way to handle it is to flip the places of csup and cvsup in the
docs. That is, where csup is mentioned as an aside now and cvsup
mentioned in the main body of the docs and examples their positions
should be swapped. The few comments in response to that suggestion were



	... and that's just a little bit of history repeating.
			-- Propellerheads

	Improve the effectiveness of your Internet presence with
	a domain name makeover!

More information about the cvs-all mailing list