> -Original Message-
> From: Bob Archer [mailto:bob.arc...@amsi.com]
> Sent: Wednesday, August 07, 2013 2:30 PM
> To: Brenden Walker; Philip Martin
> Cc: users@subversion.apache.org
> Subject: RE: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424
> -Original Message-
> From: Philip Martin [mailto:philip.mar...@wandisco.com]
> Sent: Wednesday, August 07, 2013 12:19 PM
> To: Brenden Walker
> Cc: users@subversion.apache.org
> Subject: Re: RESOLVED: SVN copy that worked in 1.8.0 now fails with (424
> FailedDep
> -Original Message-
> From: Brenden Walker [mailto:bkwal...@drbsystems.com]
> Sent: Wednesday, August 07, 2013 11:42 AM
> To: users@subversion.apache.org
> Subject: RE: SVN copy that worked in 1.8.0 now fails with (424
> FailedDependency)
>
> > -Ori
> -Original Message-
> From: Brenden Walker [mailto:bkwal...@drbsystems.com]
> Sent: Wednesday, August 07, 2013 11:27 AM
> To: users@subversion.apache.org
> Subject: SVN copy that worked in 1.8.0 not fails with (424 Failed Dependency)
>
> svn: E175002: Adding dire
svn: E175002: Adding directory failed: COPY on
/svn/Development/!svn/rvr/7020/Trunk/Projects/SiteWatch (424 Failed Dependency)
This is part of our build process which hasn't changed and worked prior to
updating to 1.8.1 yesterday (Visual SVN Server). I tested copying some other
paths and that
If you have multiple projects that may edit the shared code I would recommend
treating it as vendor code:
http://www.visualsvn.com/support/svnbook/advanced/vendorbr/
We do that with multiple in-house projects run by multiple departments and it
allows us to share changes via merging.
From: John
> -Original Message-
> From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
>
> On May 1, 2012, at 12:12, Brenden Walker wrote:
>
> > I've been trying to set properties in my repo with a command similar to:
> >
> > svn.exe propset --
I've been trying to set properties in my repo with a command similar to:
svn.exe propset --revprop -r HEAD svn:externals
"https://devsubversion/svn/Development/Trunk/Projects/XCCS/Exports@1394
Externals/XCCS"
https://devsubversion/svn/Development_TEST/Tags/SiteWatch/RC_1/Projects/SiteWatch/
sv
> -Original Message-
> From: Ben Stover [mailto:bxsto...@yahoo.co.uk]
> Sent: Wednesday, March 28, 2012 7:47 AM
> To: Subversion Users
> Cc: Nico Kadel-Garcia; Cooke, Mark
> Subject: RE: Which is the most used/best Windows Subversion server
> distribution?
>
> Hello Mark (& others),
>
> t
I suspect we've got a language barrier to get past. Sorry for the top post, on
outlook here.
I think you want to do the following:
Each developer branches Trunk to a 'personal' branch and commits work to that
branch. When a developer has code that's ready for release, he/she would then
merge
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: Monday, December 12, 2011 3:16 PM
> To: Jeff Kowalczyk; users@subversion.apache.org
> Subject: Re: svn: E170001: Unable to connect to a repository at URL
> svn://
>
> Stefan Sperling wrote on Mon, Dec 12, 2
Can you install SVN on the NAS? I'm running a QNAP NAS at home with subversion
on it.
Just an idea.
From: David White [mailto:dwr...@gmail.com]
Sent: Wednesday, August 03, 2011 7:56 AM
To: users@subversion.apache.org
Subject: Proactive Question on setting up SVN repo
We have a Blade Center do
12 matches
Mail list logo
