branch - Why is branching in SVN not good enough? -
i've heard how git has redesigned how branching works, , how svn's branching model screwed up.
i've not used svn, have no preconceptions branch should like. first looked @ git branches, , "get" it.
what practical drawbacks of svn branches?
answers pov of workflow, branching strategy , branch performance (in terms of commit/checkout/switch times) encouraged.
thanks, jrh
a few things come mind
- all branches stored in central repository. if you're not connected server, or connection slow, can't access them quickly.
- all branches stored in central repository. means they're public -- on team can view them. there's no way keep private branch no 1 else has access to.
- the dag of commits contains enough information can figure out changes included in current version of code, including changes number of branches. in svn, iirc, done using
svn:mergeinfo
property, more complicated imho, , error-prone because might forget commit changed property.
Comments
Post a Comment