Stefan, I'm not sure which you were asking for, but here's a shot at better documentation, anyway. Btw, with just a few more features I might be able to implement patch creation and submission with cvs using ant.
Julian. Index: docs/index.html =================================================================== RCS file: /home/cvspublic/jakarta-ant/docs/index.html,v retrieving revision 1.146 diff -u -r1.146 index.html --- docs/index.html 2000/11/06 14:10:56 1.146 +++ docs/index.html 2000/11/08 11:43:08 @@ -1434,7 +1434,7 @@ <h2><a name="cvs">Cvs</a></h2> <h3>Description</h3> <p>Handles packages/modules retrieved from a -<a href="http://www.cyclic.com/";>CVS</a> repository.</p> +<a href="http://www.cvshome.org/";>CVS</a> repository.</p> <p>When doing automated builds, the <a href="#get">get task</a> should be preferred over the <i>checkout</i> command, because of speed.</p> <h3>Parameters</h3> @@ -1505,6 +1505,11 @@ <pre> <cvs dest="${ws.dir}" command="update" /></pre> <p>updates the package/module that has previously been checked out into "${ws.dir}".</p> +<pre> <cvs command="-q diff -u -N" output="patch.txt"/></pre> +<p>silently (-q) creates a file called patch.txt which contains a unified (-u) diff which includes new files added via "cvs add" (-N) and can be used as input to patch.</p> +<pre> <cvs command="update -A -d"/></pre> +<p>Updates from the head of repository ignoring sticky bits (-A) and creating any new directories as necessary (-d).</p> +<p>Note: the text of the command is passed to cvs "as-is" so any cvs options should appear before the command, and any command options should appear after the command as in the diff example above. See <a href="http://www.cvshome.org/docs/manual/index.html";>the cvs manual</a> for details, specifically the <a href="http://www.cvshome.org/docs/manual/cvs_16.html";>Guide to CVS commands</a></p> <hr> <h2><a name="delete">Delete</a></h2> <h3>Description</h3> ----- Original Message ----- From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 06, 2000 6:00 PM Subject: Re: [PATCH] Cvs task: adding co -d functionality > >>>>> "JMS" == Julian M Savage <[EMAIL PROTECTED]> writes: > > JMS> I discovered that you can actually pass any options to the cvs > JMS> command directly, > > Yes, it has been broken some time, when the task used > setValue(command) instead of setLine(command). I usually have > something like command="update -d -P". > > JMS> although perhaps if the cvs task itself were better > JMS> documented/more intuitive > > want to give it a try 8-) > > Stefan >
