On Tue, Jun 26, 2012 at 02:50:33PM +, Mark Bertenshaw wrote:
> Stefan -
>
> Thanks verifying this point. As a related matter, the error code returned in
> my case just happened to be 1. Is there a list of standard error codes
> returned from SVN ?
I believe it is always either 0 or 1 at the
Guten Tag Mark Bertenshaw,
am Dienstag, 26. Juni 2012 um 16:38 schrieben Sie:
> On the other hand, I can't find an
> option for SVN ADD which says "ignore versioned files".
I think --force is what you're looking for.
svn help add
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schönin
2012 15:44
To: Mark Bertenshaw
Cc: users@subversion.apache.org
Subject: Re: Change in SVN ADD behaviour between 1.6.5 and 1.7.5
On Tue, Jun 26, 2012 at 01:58:56PM +, Mark Bertenshaw wrote:
> Hi -
>
> I have just cleared up a build issue which resulted from upgrading from
> Subv
On Tue, Jun 26, 2012 at 01:58:56PM +, Mark Bertenshaw wrote:
> Hi -
>
> I have just cleared up a build issue which resulted from upgrading from
> Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
> newly created component logs with:
>
> SVN ADD -q $APPROOT/LOG
Hi -
I have just cleared up a build issue which resulted from upgrading from
Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
newly created component logs with:
SVN ADD -q $APPROOT/LOGS/*
In both versions of Subversion, this raises an error saying that the log f
Please send plain text to the mailing list.
On Tue, Jun 26, 2012 at 9:58 AM, Mark Bertenshaw
wrote:
>
> Hi -
>
>
>
> I have just cleared up a build issue which resulted from upgrading from
> Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
> newly created component l
Hi -
I have just cleared up a build issue which resulted from upgrading from
Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any
newly created component logs with:
SVN ADD -q $APPROOT/LOGS/*
In both versions of Subversion, this raises an error saying that the log f
