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

Re: Standard setup for multiple branch merges?

From: Duncan Murdoch <subversion_at_murdoch-sutherland.com>
Date: 2004-07-24 02:33:49 CEST

On Fri, 23 Jul 2004 15:24:04 -0500, Ben Collins-Sussman
<sussman@collab.net> wrote:

>
>Let me phrase it another way: the reason your current CVS process is so
>obsessed with tag creation is because CVS has no ability to name/capture
>changesets. Incessant tagging is the *only* way to approximate that
>sort of thing: "let's see, to port this bugfix, I need to tag the tree
>before committing, and tag it after committing, and then use those tags
>to merge the change to a different branch."
>
>In Subversion, the tagging isn't necessary. You just "port change r3981
>from branchA to branchB". All the correct files are part of the
>changeset already.

Thanks again. This sort of advice is very helpful.

The reason I'm asking this is that I'm revising the document

 <http://developer.r-project.org/CVStips.html>

to apply to Subversion instead of CVS. This page tells how to check
out working copies, commit changes, etc. You don't happen to know of
similar project-specific advice for some other project that I could
steal^H^H^H^H^Hconsult, do you?

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 24 02:34:10 2004

This is an archived mail posted to the Subversion Users mailing list.