Re: unique branch problem

Hello,

John Joseph Bachir wrote:

> [1] is there a better, Best Practices way for me to manage my "rogue
> branch"? If not...

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

> [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.

Albert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 21 09:29:41 2005