[python-committers] Is 3.1 open?
Nick Coghlan
ncoghlan at gmail.com
Wed Mar 17 22:41:06 CET 2010
More information about the python-committers mailing list
Wed Mar 17 22:41:06 CET 2010
- Previous message: [python-committers] Is 3.1 open?
- Next message: [python-committers] Is 3.1 open?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benjamin Peterson wrote: > 2010/3/17 Nick Coghlan <ncoghlan at gmail.com>: >> Short version: SVN and other non-DVCS systems don't store enough (or the >> right) metadata to support merging properly, so branching becomes >> unnecessarily painful. > > This isn't really true these days given svn merge --reintegrate. File renaming/moving still doesn't work properly though: http://blogs.open.collab.net/svn/2008/07/subversion-merg.html There are limits to what you can do without tracking the original changesets. A DVCS does that, but SVN works by calculating diffs between different revisions without really caring about how those revisions came about. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
- Previous message: [python-committers] Is 3.1 open?
- Next message: [python-committers] Is 3.1 open?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list