Derek R. Price writes:
>
> I was thinking about
> creating differing error levels for fatal and non-fatal errors,
That can be somewhat tricky. Standard C only defines two portable exit
statuses -- success, represented by 0 or EXIT_SUCCESS; and failure,
represented by EXIT_FAILURE. Using any ot
-
>
> Date: Mon, 09 Oct 2000 18:37:21 -0400
> From: "Derek R. Price" <[EMAIL PROTECTED]>
> Organization: Open Avenue
> X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.0-test1 i686)
> X-Accept-Language: en
> To: Rob <[EMAIL PROTECTED]>
> CC: [EMAIL PR
Rob wrote:
> Is there any way to tell CVS that I want to
> add only new files to the repository? Perhaps if
> I "cvs diff $file" and check the error level for
> each file?
I just checked in a change to allow '-q' to suppress those warnings.
CVS will still exit with an error code, however. Not s
On Fri, Oct 06, 2000 at 08:33 -0500, Richard J. Duncan wrote:
>
> Then run,
>
> find . -type f -exec foo.pl {} \;
An exec for every single item found is quite expensive (don't
know about today's timing, but I would estimate some 10 msec for
creating a new process -- the perl compiler run adds t
thing like
this:
@findResults = `find . -type f -exec foo.pl {} \;`;
In this case "find" is from the Cygwin or MKS tools.
-Scott
-Original Message-
From: Richard J. Duncan [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 06, 2000 6:33 AM
To: [EMAIL PROTECTED]
Subjec
> Is there any way to tell CVS that I want to
> add only new files to the repository? Perhaps if
> I "cvs diff $file" and check the error level for
> each file?
One easy way is to run `cvs status ` and grep for "Status:
Unknown." Pipes don't work well in a find command, so I generally
write a qui
e new files involved.
The way I do this now is a simple "cvs add `find ./`"
This does work, but puts out a horrendous amount
of output that I simply throw away ( normally
the scripts checks for error levels following each
command, but in this case the level is always "1"
with a
