This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using up double diskspace for working copies (Was Re: Detailsfor svn test repository)
> Right - using svn programs to directly modify the svk depot (which is it's
> local 'repository'), is touchy. You *can* do it, but you have to be quite
> careful about the svk:* properties used to track merges and mirrors.
> Generally there's no need, other than perhaps using a read-only client to
> make your local work visible to others prior to pushing it upstream.
>
> However, none of this doesn't mean you can't use svk as your local client
> with a normal svn repository mirrored into the depot. In fact, it's
> probably the most common use of svk. This is *not* a readonly setup, as svk
> knows how to push commits through and back to upstream. Obviously this can
> entail conflict resolution if your local mirror has become a local branch,
> since svk also allows you to make commits that you haven't pushed back up
> yet, but that's not really different than still having it all loose WC
> without a local VCS.
Oh, okay, i get it now.
:)
Thanks for all the clarficiation