RE: Approaches to forking code

> The way I see it, there are 4 approaches to forking code:-
>
> 1. Just copy
> 2. Make expensive copies
> 3. Create a new repository and import
> 4. Create a copy of the existing repository

Isn't a fork really just a another name for a branch? I think using svn
cp URL URL is the best solution for this. I think the main difference
between a banch and a fork is perhaps where you copy to in your repo.

For example... you might do this to branch:

Svn cp http://server/repo/project/trunk
http://server/rept/project/branches/branchname

Where as to fork (create a new project based on current project) you
might do:

Svn cp http://server/repo/project/trunk
http://server/repo/NEWproject/trunk --parents

Now in your repo you have:

Project
 -trunk
 -tags
 -branhes
Newproject
 -trunk

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1038095

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-20 16:17:40 CET