[03:24] <jam> lifeless: if you get a chance, I have an analysis of bug #507566 that could use another person with fairly intimate knowledge of the pack internals. I'm technically on a 3-day weekend
[03:59] <lifeless> jam: I'm on 3 1/2 days leave + 4 days conf leave :). I'll have a look though.
[04:00] <jam> lifeless: certainly, don't spend a huge time on it
[04:00] <jam> you're just the best for the job :)
[04:00] <fullermd> jam: Hey, I had an offhand question for you...
[04:01] <fullermd> jam: I recall some months back there was a discussion about pyrex versions and some advantage or other that could be had in the Cish code if it could be written ignoring pyrex and using cython.
[04:02] <jam> fullermd: 'cdef list foo'
[04:02] <jam> will auto-use stuff like PyList_Append()
[04:02] <lifeless> jam: sounds plausible to me
[04:02] <jam> also, if you have a Cython class that has to 'object' members, it doesn't get a GC header
[04:02] <fullermd> Are you aware of any advantage that using cython instead of pyrex would convey with the current code?
[04:02] <jam> 'has to' => 'has no'
[04:03] <lifeless> jam: I'd need to drop into a debugger to be more confident than that
[04:03] <jam> lifeless: that's where I got the idea (in debugger)
[04:03] <jam> fullermd: cython generates slightly faster code.
[04:03] <jam> it uses stuff like "likely()" macros, etc
[04:03] <jam> it isn't a huge diff
[04:03] <jam> but it is there
[04:04] <fullermd> Are release tarballs built with cython?
[04:04] <fullermd> (and/or should they be?)
[04:05] <fullermd> Sorry, I'm wandering way past my offhand question...  don't wanna bother you this late.
[04:23] <Peng> There are also some hacks in the code for Pyrex compatibility.
[08:01] <freelanc> i am getting this error while trying to resolve diverged branches http://pastebin.com/m59e08642
[11:03] <bialix> hi
[11:03]  * bialix looking for nmb
[11:03]  * bialix sighs
[12:49] <bsdemon> Hi, can I get content of versioned file without working tree, using only bzrlib.branch.Branch? Or I need to do a checkout
[13:01] <chx> hi. two plugins questions. i branched something , the bzr dir was 66m , ran bzr index and now it's 97m is it normal that the index of 10mb worth of files is 31m? another thing, i checked out bisect, ran the python setup.py build_ext -i command and bzr selftest bisect and it was OK (37 tests) but it can't find the command bisect and bzr plugins does not list it.
[14:47] <Peng> D'oh, chx left. Those 37 tests aren't related to the bisect plugin...
[16:55] <tumbleweed> quick Q: doing a big file re-organisation in a bzr-managed project
[16:55] <tumbleweed> is there way to carry history accross when merging multiple files
[16:55] <tumbleweed> bzr mv-style
[19:38] <thumper> abentley: ping
[19:51] <abentley> thumper: pong
[19:52] <lifeless> its too early for that sort of thing
[19:56] <abentley> lifeless: look who's talking.
[20:45] <lifeless> abentley: :)
[20:45] <lifeless> abentley: around? got a small feature request for lp code notification emails
[20:46] <abentley> lifeless: Just leaving.
[20:46] <meoblast001> what's the name of the bazaar config file?
[20:46] <lifeless> abentley: ah, kk. Just kirkland wondering if he can get a link to loggerheads commit view in the notification
[20:48] <Peng> meoblast001: Which one?
[20:48] <meoblast001> the one that lets me set my email
[20:49] <Peng> meoblast001: You can do that with "bzr whoami".
[20:49] <meoblast001> ah, ok
[20:49] <Peng> meoblast001: But, FYI, depending on the platform, it's probably ~/.bazaar/bazaar.conf. "bzr version" will show you the location.
[20:50] <Peng> s/location/directory.
[20:51] <meoblast001> Peng: i usually use my Ubuntu system at home but i'm using my Fedora laptop
[20:51] <meoblast001> i like consistant names in my email