[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: unique branch problem

From: John Joseph Bachir <johnjosephbachir_at_gmail.com>
Date: 2005-10-21 16:35:31 CEST

> You could consider the OS project to be a vendor, and use a vendor branch
> instead. This is covered in the svn book.

Great, I will read up on it.

> [2] as an experiment i tried this on an export (not checkout) of my code,
> > and it didn't work. svn complained that . was not a working copy. This
> made
> > me suspicious since, of course, the local .svn information had nothing
> to do
> We probably need the command you tried here. I personally never exported
> anything from svn, but I would not expect that you need a working copy in
> order to export a project.

Just the command i mentioned.

svn merge -r<previous>:<current> http://example.com/project/trunk

If I do that inside of a checkout of my project, it works. If i do that
inside of an export of my project, it complains.
Received on Fri Oct 21 16:43:06 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.