Alex,
the command to use to create a copy without svn metadata (if this is your
intention) is:
svn export /usr/src/svn/php-3.2.0 /some/target/path
You're getting the error because you are trying to access the working copy, but
due to the file:/// prefix subversion expects this to be the locatio
I have subversion copy of repository ex. php-3.2.0
path: /usr/src/svn/php-3.2.0
when im in this folder i can do anything: svn update, svn info, svn log
and everything is work well. but if i want to make a non subversion
copy: svn co file:///usr/src/svn/php-3.2.0 /usr/src/php-src
svn doesn't do
Hi,
I've just come across an interesting scenario, which did not work as I
expected.
I created a feature branch several months ago, and have been keeping it up
to date from trunk periodically. There was a change towards the start that
was required on the branch, but I did not want merged into tru
Hi,
I have one repository with the development tree of some templates.
Those templates are exported to projects that might customize the
templates. The copy of the templates is added and committed to the
project repository. In the projects the latest changes in the template
development tree
Stefan Sperling wrote on Fri, 28 May 2010 at 01:22 +0200:
> I think Daniel means
No, that's not what I meant.
On Wednesday 12 May 2010, Andy Levy wrote:
> On Wed, May 12, 2010 at 09:23, Vadym Chepkov wrote:
> > I think the exit code subversion returns isn't right, it should indicate
> > an error
[...]
> > $ svn update /etc
> > Skipped '/etc'
> > $ echo $?
> > 0
>
> Why? The command executed successfully a
