First is to do an "svn cp" of the tree from the revision prior to that "svn rm" command back into its current location. Given SVN, that's a very cheap copy, but it'll break a lot of "svn log" information. If you don't care, that's the way to go. (I've done this before.) Something like:
svn cp http://repos/company/projects/project@REVhttp://repos/company/projects/projectAlternate solution if you really want it reversed is to make both a full and incremental backup of the current state, then restore the whole repository from your most-recent full backup before the undesired command, and then replay the incremental backup into that, stopping at the revision just before the desired command. Depending on how recent that most-recent full backup is, that may or may not take a while -- if you don't have one, I think you'd basically get to replay from start, which will
( ... )
Comments 4
First is to do an "svn cp" of the tree from the revision prior to that "svn rm" command back into its current location. Given SVN, that's a very cheap copy, but it'll break a lot of "svn log" information. If you don't care, that's the way to go. (I've done this before.) Something like:
svn cp http://repos/company/projects/project@REV http://repos/company/projects/projectAlternate solution if you really want it reversed is to make both a full and incremental backup of the current state, then restore the whole repository from your most-recent full backup before the undesired command, and then replay the incremental backup into that, stopping at the revision just before the desired command. Depending on how recent that most-recent full backup is, that may or may not take a while -- if you don't have one, I think you'd basically get to replay from start, which will ( ... )
Reply
(I'd found most of this already, but not one crucial little snippet)
Reply
Reply
Reply
Leave a comment