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

RE: Approaches to forking code

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Tue, 20 Jan 2009 10:15:09 -0500

> 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

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:




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

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.