> Want to address my note about retrospective branching?
As I think about it, restrospective branching corresponds
to copying, not just a single revision, but to copying
multiple revisions, a range of revisions,
to a new position in the Subversion
directory tree.
Something like
svn copy -r250:HEAD project project.retro-branch
svn merge -rHEAD:250 project
svn ci --messsage 'creating restrospective branch \
for changes accidentally on head \
moving them to project.retro-branch'
Possibly even
svn mv -r250:HEAD project project.retro-branch
svn ci --messsage 'creating restrospective branch \
for changes accidentally on head \
moving them to project.retro-branch'
if you take a Stalinist view of history.
i.e. if you want to be able to revise history
- which I think that you might want to be able to do,
so long as there is an underlying meta-history
that is not revised.
I.e. in the first level history revisions 250:HEAD
would no longer be visible as ever having been on the trunk;
but in the underlying meta-history they would be.
However, even without the Stalinist meta-history editing,
svn copy -r250:HEAD project project.retro-branch
seems useful for restrospective branching.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 25 22:14:23 2004