[00:20] <meth> is there something like tig for bzr ?
[00:24] <treaves> If there is not, no one here would know, as no one here would know - or care - what 'big' is.
[00:24] <treaves> ^big^tig
[00:25] <poolie> http://jonas.nitro.dk/tig/
[00:25] <poolie> a curses gui
[00:25] <poolie> no, i'd recommend using the actual gui
[00:25] <poolie> qbzr/bzr explorer
[00:25] <poolie> looks useful
[00:25] <spiv> Or even the actual cli :)
[01:43] <thomi|work_> wgz: thanks!
[09:04] <mgz> morning all
[10:53] <mgz> argh, the command hooks again
[10:53] <mgz> these tests are all broken
[10:56] <mgz> ha, and fixing the test makes it fail spectacularly.
[11:59] <jelmer> mgz: :-S
[12:02] <mgz> what's the best help we have on using scenarios? I just poke around the code base looking for examples each time
[12:02] <mgz> and have no idea of the best way of doing things.
[12:02] <mgz> ...using scenarios here is probably a dodgy idea, but amusing.
[12:04] <jelmer> mgz: that's what I do too..
[12:13] <jelmer> mgz, vila: Could I persuade either of you to have a look at my lazy-regex-pickle branch?
[12:15] <mgz> ...that's actually what I was going to do before I got distracted
[12:18] <mgz> I wonder if 246 tests is too many... :)
[12:20] <jelmer> 246 tests for what ? :)
[12:21] <mgz> option help :D
[12:23] <jelmer> hmmok :)
[12:57] <CaMason> hi guys. Is there a viable way to squash commits (without a merge operation)?
[12:57] <CaMason> so for `A-B-C-D-E-F`, I'd like `A-----D----`
[12:57] <CaMason> I figure I can do the second part with 3 uncommits, followed by a commit. But I couldn't go any further back
[13:01] <CaMason> I suppose I could `bzr diff -r A..C > squashA.patch` & `bzr diff -r D..F squashB.patch`, uncommit back to A, then patch, commit, patch, commit
[13:01] <mgz> shelve works
[13:01] <mgz> avoids messing around with patches
[13:02] <CaMason> uncommit F-D, shelve, uncommit C-A, commit, unshelve, commit?
[13:03] <mgz> right.
[13:04] <CaMason> I could also re-order with shelving too
[13:04] <CaMason> great. That completley complements our Git workflow
[16:16] <mgz> jelmer: could you set aside some time this week to team up on reviewing MvG's lazy import branch?
[16:19] <jelmer> mgz: sure
[16:19] <jelmer> mgz: that reminds me, could we perhaps talk through some of the HPSS reviews?
[16:20] <mgz> sounds like a good thing to do at the same time.
[16:20] <jelmer> cool
[16:24] <mgz> I'm working from town tomorrow, so how about we say Friday, or do you think we can fit it all in the rest of today?
[16:25] <jelmer> friday works for me
[20:47] <beuno> o/
[20:47] <beuno> quick quesiton
[20:47] <beuno> how would I run a plugin's command from python?
[20:48] <beuno> I'm integration qbzr into an IDE written in python
[20:48] <beuno> and I want the context manu to bring up qbzr's commit dialog
[20:49] <mgz> do you want to yield execution to qbzr?
[20:49] <mgz> if not, use subprocess.call
[20:50] <mgz> otherwise, there are a couple of steps, but it's similar to calling a bzrlib command
[20:53] <beuno> I guess I could just subprocess it
[20:54] <mgz> you'll need to work with the qt main loop otherwise, which may or may not be an issue for you.
[20:54] <beuno> it's a QT app, but also, I ahve zero experience with QT  :)
[20:56] <mgz> ah, you're doing the qt creator integration?
[20:56] <mgz> or a different qt ide... you said written in python...
[20:58] <mgz> starting with subprocess isn't bad, but I recommend a post to the bazaar list with some details, as something more integrated may be preferable
[21:01] <beuno> different
[21:01] <beuno> ninja-idea
[21:02] <beuno> yeah, I'll get the basics with subprocess
[21:02] <beuno> and email the list
[22:00] <poolie> goofd morning, hi beuno
[22:02] <jelmer> hey poolie
[22:16] <poolie> hi there
[22:44] <lifeless> ♥ jelmer
[23:07] <jelmer> hi lifeless, what's with the question mark?
[23:12] <james_w> heh
[23:20] <poolie> haha
[23:21] <poolie> hi james
[23:24] <lifeless> jelmer: hah, surely your utf8 setup works ;)
[23:37] <jelmer> lifeless: hah, I see it now.. :)
[23:37] <jelmer> lifeless: glad you like it