[00:06] sproaty: you can replace the content of the repo's working directory with the code and commit it. or alternatively make unified diff an apply it [00:13] ccxCZ, so copy my current dir contents somewhere, checkout my branch into that folder then move my back over? [00:13] move my code* [00:19] it's one of possibilities, actually I'd rather suggest rsync -av --delete --exclude .bzr code/ new_branch/ [00:20] that will make sure you leave the .bzr dir intact and copy over all files along with permissions etc. [00:22] I'd make a temporary branch, rm away all the files in the WT, then move the .bzr dir into the existing place. [00:22] (well, I guess you could skip the rm'ing and just mv .bzr) [00:22] that's also an alternative [00:23] on windows unfortunately :( [00:24] well, then the trick with moving .bzr is more easilly done I guess [00:29] cheers :) [09:26] Sorry for the spam, but any Australians here going to UDS on Qantas tomorrow? === michaelh1 is now known as michaelh1|away [18:36] hello [18:39] how can i get a previous revision of my launchpad tree? [18:41] (revert to the previous) [18:58] hikiko: bzr revert -rREV [18:58] hikiko: if you also want to change the branch back, use "zr update -rREV" [18:59] thank you :) [18:59] hmmm it doesn't download anything [19:00] i added some textures (png images) to my branch previous revision [19:00] and now i want them back without checking out and then copy and then commit etc [19:00] is this possible? [19:01] hikiko: it doesn't need to download anything as it has the local history [19:01] no [19:01] (assuming you didn't use a light weight checkout) [19:01] i replaced them [19:01] with low resolution textures [19:02] and now i want the previous high resolution [19:02] from the previous release [19:02] In that case you want to use 'revert' on those files. [19:04] bzr revert file 1 file2 etc? [19:05] revert -rWHATEVER file1 file2 ... [19:07] thank you :) [23:09] hm, apparently it's midnight back home.