Re^2: [OT] Best Use of Subversion Branches in Perl Development

I've only been using svn @ $work and never really got into it, so thanks for the extensive explanation. I've read all the thread in detail, and followed the links provided. Many interesting ideas here! Hopefully, I'm learning something.

Regarding the specific issue being discussed here, since versioning control systems keep track of what's getting modified anyway, it seems strange that there's not a "selective" cp command that will copy one branch over another without overwriting files that have been modified in the destination one. If there were, then the OP would issue it before running the tests, resolve problems, and then merge.

Comment on Re^2: [OT] Best Use of Subversion Branches in Perl Development Select or Download Code

Replies are listed 'Best First'.
Re^3: [OT] Best Use of Subversion Branches in Perl Development by perrin (Chancellor) on Mar 05, 2007 at 14:32 UTC
That wouldn't really be enough. You have to get the changes to the files you have modified as well. The svn merge command is pretty good at this though.	[reply]
Re^4: [OT] Best Use of Subversion Branches in Perl Development by blazar (Canon) on Mar 05, 2007 at 21:14 UTC
That wouldn't really be enough. You have to get the changes to the files you have modified as well. The svn merge command is pretty good at this though. D'Oh! /me slaps his forehead. I found the reading of this thread stimulating, though, and I've started a new one, that I've been meditating about for some time now, somewhat related to these issues.	[reply]