from have understood, branch directly copied trunk.
say have developer , b. wants work on project, creates branch1 , copies trunk branch1. works in branch1. there scenario b want work in branch1 well?
it seems me if b wants work on project, create branch2 trunk instead of working on same branch. spirit of svn?
no, not true.
a branch can copied of every repository subtree. in cases it's /trunk or other branch.
say have developer , b. wants work on project, creates branch1 , copies trunk branch1.
creating branch operation copy itself. creates branch points trunk. it's called "cheap copies", concept similar symlinks.
he works in branch1. there scenario b want work in branch1 well?
yes, it's common scenario. example, branch feature branch , multiple developers can working on it.
it seems me if b wants work on project, create branch2 trunk instead of working on same branch. spirit of svn?
it depends on particular case , branching model use. it's totally ok , b work on same branch.
Comments
Post a Comment