Working Copy at multiple levels

[Kit Marshall <ki...@crystalmoments.net>]

I am using Subversion to track changes to websites that I am working
on.  The sites are all on the Apache web server and in the svn repository
as well and I don't always keep the entire sites locally on my pc.  What
I'm attempting to do is check out something like
repos/siteroot/public_html/clients/portfolio and work on that directory
but then be able to check out repos/siteroot/public_html/aboutus and
work on that folder and possibly repos/siteroot/includes as well (for
example).  But this causes there to be a working copy at each level I
checked out which in turn causes problems adding new files or
updating/committing code changes.

I realize that if I check out repos/siteroot and get the entire site then I
could work at any level without issues but this would require me to have
the entire site locally (not the end of the world but I was trying to avoid
this).  Am I just working against the intentions of Subversion or is there
some easier way to work in different areas of a project without having
the entire project locally and without using the
"check out/modify/commit/delete working copy" method?

Thanks for your help!

Kit Marshall
Crystal Moments Creative



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Working Copy at multiple levels

[Ryan Schmidt <su...@ryandesign.com>]

On Mar 18, 2006, at 20:33, Kit Marshall wrote:

> I am using Subversion to track changes to websites that I am working
> on.  The sites are all on the Apache web server and in the svn  
> repository
> as well and I don't always keep the entire sites locally on my pc.   
> What
> I'm attempting to do is check out something like
> repos/siteroot/public_html/clients/portfolio and work on that  
> directory
> but then be able to check out repos/siteroot/public_html/aboutus and
> work on that folder and possibly repos/siteroot/includes as well (for
> example).  But this causes there to be a working copy at each level I
> checked out which in turn causes problems adding new files or
> updating/committing code changes.

It should work fine. What's the problem? That is, what doesn't work?

Any part of the repository can be checked out and checked into. You  
can make as many working copies of whatever parts of the repository  
as you want.

svn checkout \
http://example.com/repos/siteroot/public_html/clients/portfolio

svn checkout \
http://example.com/repos/siteroot/public_html/aboutus

svn checkout \
http://example.com/repos/siteroot/includes

Now you have three separate working copies in the current directory  
on your computer, called portfolio, aboutus and includes, which can  
be edited and committed at will.

You cannot, however, make a change to two or more of these  
directories and expect to be able to commit the changes as a single  
revision, unless you have checked out the entire common parent  
directory.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org