It will still return an error code of '1' in both cases. I was thinking about
creating differing error levels for fatal and non-fatal errors, but I thought this
would require more discussion before adding to the CVS API. I was also thinking of
abolishing the error codes in add's non-fatal case altogether. This would match the
behavior of 'cvs remove' (short of the additional warning message) but I wasn't sure
whether this would have any far-reaching repercussions which would be better
avoided.
Comments?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I am not a dentist.
I am not a dentist.
I am not a dentist...
- Bart Simpson on chalkboard, _The Simpsons_
Robert Helmer wrote:
> cool.. this is pretty cool way to do it, will
> it give an error code of "1" or will it be
> errorlevel that means "file already exists"?
>
> That way I could differentiate between fatal
> and non-fatal errors reliably.
>
> ----- Forwarded message from "Derek R. Price" <[EMAIL PROTECTED]> -----
>
> 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 PROTECTED]
> Subject: Re: cvs add `find ./`
>
> 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 sure if this is
> optimal. Let me know.
>
> The patch against the dev version is attached in case you want it
> early. I expect it should work against 1.11.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
