[00:16] <jelmer> hi poolie, wgz
[00:16] <jelmer> m4n1sh: pong
[09:14] <mgz> morning all
[09:23] <vila> morning mgz !
[10:36] <jelmer> hah, mgz beats me in replying to erik's mail
[10:37] <mgz> :)
[10:37] <mgz> I normally lose that race
[10:38] <mgz> I'm used to hitting reply and seeing a response from jelmer 4 minutes before
[10:38]  * jelmer is having a slow day
[15:00] <mgz> hm, vila left just when I was going to bother him with some questions
[15:59] <vila> mgz: (gentle nudge) bzr-2.6b1 windows installers ?
[16:01] <vila> maxb: beta ppa update for 2.6b1 ?
[16:02] <fullermd> vila: 2.6.0 release?   :p
[16:02] <vila> hehe, I'm already late for 2.5.1, but I'm really ahead of schedule for 2.6.0 :-D
[16:03] <mgz> vila, things are pretty borked right now
[16:03] <vila> mgz: can you elaborate ? :-)
[16:04] <mgz> well, explorer won't start without the mp jelmer submitted this morning
[16:04] <mgz> gordon needed to backport your change from post-2.6b1?
[16:04] <mgz> the installer work for translations still needs doing
[16:05] <mgz> there's not much point doing release stuff without fixing the code problems
[16:05] <fullermd> For Windows?  Why not?  Microsoft has been doing it for years...
[16:05] <vila> Can you summarize in a mail to the list ?
[16:06] <vila> gordong did release an osx installer, which change are you referring to ?
[16:06] <vila> oh, right, sry
[16:06] <vila> let me check
[16:07] <vila> yeah, it did include the fix for building the docs,
[16:08] <vila> no comma, just read it as a period ;0)
[16:08] <vila> oh crap, my printer is borked...
[18:20] <m4n1sh> is there a code snippet using which I can find the list of files changed for a bzr working tree using bzrlib?
[18:35] <mgz> m4n1sh: something like...
[18:36] <m4n1sh> like if I have a WorkTree
[18:36] <m4n1sh> I used open to open a repository
[18:36] <m4n1sh> and then want to goto a specific commit number
[18:36] <m4n1sh> mgz: and fetch the list of files changed/added/deleted in that commit
[18:37] <mgz> >>> from bzrlib.workingtree import WorkingTree
[18:37] <mgz> >>> tree = WorkingTree.open(".")
[18:37] <mgz> >>> lock = tree.lock_read()
[18:37] <mgz> >>> list(tree.iter_changes(tree.basis_tree()))
[18:37] <mgz> see the docstring in the code for what the bits of the tuple mean
[18:37] <m4n1sh> how do I pinpoint to a specific commit?
[18:38] <m4n1sh> I know iter_changes, but the name of that argument it takes was sort of cryptic
[18:38] <mgz> pass something other than basis_tree
[18:38] <m4n1sh> like?
[18:38] <m4n1sh> say I have a commit number 343
[18:38] <m4n1sh> then how do I use that method
[18:39] <m4n1sh> I was stuck on iter_changed method for an hour becuase I did not figure out  how to use it for a specific revision number
[18:39] <mgz> you turn the number into a revid, then pass the revid to revision_tree()
[18:41] <mgz> that's using branch and repository respectively
[18:45] <mgz> eg:
[18:45] <mgz> >>> branch = tree.branch
[18:45] <mgz> >>> prev_tree = branch.repository.revision_tree(branch.get_rev_id(728))
[18:45] <mgz> >>> list(tree.iter_changes(prev_tree))
[18:45] <mgz> iterates over changes between r728 and the current tree state
[18:47] <mgz> same principle if you want the differences between r728 and r729, you just get two prev trees (and can open and lock the branch rather than the working tree in the first place)
[18:47] <mgz> m4n1sh: does that help?
[18:48] <m4n1sh> mgz: trying it out
[19:03] <m4n1sh> mgz: works
[19:03] <m4n1sh> I get
[19:03] <m4n1sh> ('configure.ac-20110725232344-gqsb35ufn2i0pf3g-9', (u'configure.ac', u'configure.ac'), True, (True, True), ('tree_root-20110725232341-3el21lx99g2juau0-1', 'tree_root-20110725232341-3el21lx99g2juau0-1'), (u'configure.ac', u'configure.ac'
[19:03] <m4n1sh> ), ('file', 'file'), (False, False))
[19:04] <m4n1sh> now how do I make out if this file configure.ac is added/removed/edited?
[19:07] <mgz> as I said, see the docstring (in bzrlib/tree.py InterTree.iter_changes)
[19:08] <mgz> the (source, target) tuple at [1] tells if you it where added, removed, or renamed
[19:09] <mgz> the changed_content marker at [2] tells you if it was edited
[19:10] <mgz> so, your example the file was changed that rev
[19:12] <mgz> see the code in bzrlib/delta.py for code doing this kind of thing
[19:12] <mgz> report_changes there takes a tuple in that form and makes pretty output
[20:43] <caliboy> hello
[20:43] <mgrandi> hey
[20:44] <caliboy> can you help me with my wireless network
[20:44] <mgrandi> uhh sure, does this have anything to do with bzr though? :o
[20:44] <caliboy> no
[20:45] <mgrandi> then why ask here? =P
[20:47] <caliboy> idk i didnt know there was a categories thing
[23:40] <kbulgrien> ok, well, it is on ml now