the Adib-2 wrote

...

bzr checkout lp:inkscape-devlibs64 \devlibs64 bzr revno ->tells me rev 16 bzr revert -r14 bzr revno ->tells me rev 16 bzr update bzr revno ->tells me rev 16

bzr revert -r14 alone is enough if you only want the files on disk to go back at revision 14. bzr revno still reports '16' because the history is actually at revision 16 and all the backed-up file result as being modified (as if you had typed by hand all the modifications to go back to rev 14). Now, if you commit you'll get the new rev 17 being identical to rev 14.

If you want some feedback in the history that you went back at revision 14 you have to: bzr update -r14 In this way the log will report the working tree to be at revision 14 but in the history versions 15 and 16 will still be listed (as "future" versions) and revno will still report '16'. Now, if you commit you'll get a "working tree out of date, please run update" message because your position in the history is not the latest so you cannot add a new step from your position, you first have to move to the end (or start a new parallel branch, but this is another story).

I hope this explanation is correct and clear enough. Luca

-- View this message in context: http://inkscape.13.x6.nabble.com/bzr-howto-change-to-specific-revno-tp497252... Sent from the Inkscape - Dev mailing list archive at Nabble.com.