[17:34] beginner question: what is bzr's equivalent of "git checkout COMMIT" and "git checkout master"? [18:25] hello, what is the Bazaar equivalent of 'git checkout X' and 'git checkout master'? [18:33] Er... bzr checkout URL presumably..? [18:48] I need to examine an old revision of the code, how is that down it bzr? [18:49] *how is that done in bzr? [18:49] -r123 [18:49] or whatever the revision number [18:49] bzr checkout -r123? [18:49] -rtag:SOME_TAGNAME [18:51] bzr checkout -r1 --> "File exists .bzr" [18:51] (sorry I'm very new to bzr) [18:51] Oh... in an already checked-out directory..? [18:52] revert [18:53] Or checkout in a new dir. [18:53] LeoNerd: that worked! thank you! [18:54] cd ..; bzr co -r123 existindir newdir [18:56] LeoNerd: that is very helpful :) how would you revert back to the latest revision? [18:57] bzr revert [18:57] Or maybe revert -r-1 [18:57] Negative revision numbers count backwards from head [18:58] LeoNerd: that's a nice shortcut [18:59] Highly useful [19:00] -c is also useful; represents a change rather than a revision.. -c 10 is the change committed at 10; i.e. between -r 9 and -r 10. Useful for diff, etc.. [19:00] bzr di -c-1 # last committed change [19:04] LeoNerd: very useful, I'm trying to learn about the dev progress of an opensource project by reading its revisions step by step, so that's definitely going to help! [19:05] Yup, can be handy [19:06] Hopefully the project lays tags periodically, perhaps on releases and so on... I tend to do that.. bzr tags should list them [19:06] Can be useful points to compare between [19:08] LeoNerd: yes, it does (the project is Zim) [19:11] LeoNerd: when/how often would you tag revisions? [19:14] Well, about 90% of my bzr work is Perl modules for CPAN; so I create a tag per numbered release [19:21] LeoNerd: I see... [19:27] LeoNerd: thank you for your useful tips, it helped to speed up my bzr learning progress :o) [19:28] :) [19:46] how would you look for a file in all revisions? [19:50] How do you mean? [19:52] I mean searching all revisions to find a file (for current revision I just do find -name "x") [19:55] What do you mean "to find a file"... [19:56] e.g. I want to see what revisions have a file named "setup.py" [19:57] Oh.. well presumablly all of them since it was added.. no? [19:58] is there any way to find out when (in which revision) it was added? [19:59] Something like "file history"..? [19:59] I forget quite; it's not a query I usually make. Prettysure it exists, though [20:04] ah yes, I searched for it, it's "bzr log filename" (the file must exist in the current revision) [20:07] Ahhyes === sina is now known as sinas === JasonO_ is now known as JasonO [23:25] good morning [23:27] hi jelmer [23:28] 'morning poolie [23:41] hey there [23:43] poolie: I went through the bfbip LEP the other day to see if there were any requirements that hadn't been addressed yet [23:43] poolie: It seems like the main thing that's not well defined yet is the security requirements [23:44] perhaps we should have a u-d-d or u-d thread about that? [23:44] or, perhaps make some more concrete proposals in the lep first [23:45] poolie: related, I wonder if it would make sense to split bfbip up into bfbia (build from branch into archive) and bfbip (build from branch into primary) [23:45] the first meaning building eg into a ppa, but with no recipe? [23:46] yep, basically - just being able to say from an API call "please build this revisions from this branch into that archive" [23:46] and then the second would be mostly about just the policy change of letting it go into the primary archive [23:46] that makes sense to me [23:46] thanks for looking at this more [23:49] glad to be able to work on this :) [23:50] I'll gather thoughts and send an email to u-d-d this week [23:51] ok [23:51] i'm going to do another pass over the user documentation today [23:51] both to pick out nits, and for larger changes [23:52] ah, cool [23:56] poolie, Is all the documentation under https://wiki.ubuntu.com/DistributedDevelopment/Documentation or is there more? [23:57] ah i actually meant the general bzr documentation [23:57] but yes [23:58] hm, there might be some more in a separate packaging guide (draft?) by barry, that's integrating some of this