The lp:blender branch is mapped to the https://svn.blender.org/svnroot/bf-blender/trunk/blender subtree off of the root of the https://svn.blender.org/svnroot subversion repository root and the lp:blender/4.x branch is mapped to https://svn.blender.org/svnroot/bf-blender/branches/blender2.4/. In the process of being mapped to bazaar, a new revision identifier use by bazaar is generated for each commit. A bazaar tag containing the "svn revno" of the subversion repository commit is also stored with each revision in the bazaar branch.
This may present a problem for bugs that reference specific subversion revino in the blender.org svn tree. Is it necessary or desirable to map the new location of the commit in the bazaar tree?
The lp:blender branch is mapped to the https:/ /svn.blender. org/svnroot/ bf-blender/ trunk/blender subtree off of the root of the https:/ /svn.blender. org/svnroot subversion repository root and the lp:blender/4.x branch is mapped to https:/ /svn.blender. org/svnroot/ bf-blender/ branches/ blender2. 4/. In the process of being mapped to bazaar, a new revision identifier use by bazaar is generated for each commit. A bazaar tag containing the "svn revno" of the subversion repository commit is also stored with each revision in the bazaar branch.
This may present a problem for bugs that reference specific subversion revino in the blender.org svn tree. Is it necessary or desirable to map the new location of the commit in the bazaar tree?