[00:00] <jelmer> Noldorin: yeah, that doc is in the main branch - has been for a number of years :)
[00:00] <Noldorin> jelmer, does it though? i didn't think bzr init actually copies data from any other branch
[00:00] <Noldorin> ok
[00:00] <jelmer> Noldorin: it copies data, but just the data that is relevant *for the new branch*. It doesn't copy a lot of other data that would still be valid because other branches, either in the same repository or in stacked branches, rely on it.
[00:01] <jelmer> s/valid/necessary/
[00:01] <Noldorin> ah
[00:02] <Noldorin> jelmer, eek, what's the command to do a shallow branch again? i'm just trying to get lp:bzr now, but i don't want it to be however many GB the full rev history would fill on my system heh
[00:03] <Noldorin> jelmer, do i just want a stacked branch maybe?
[00:03] <jelmer> Noldorin: FWIW the repository is 70Mb, not GB
[00:04] <jelmer> Noldorin: --stacked
[00:04] <Noldorin> oh right
[00:04] <Noldorin> i thought it would be a lot larger!
[00:04] <Noldorin> that's surprisingly small
[00:04] <Noldorin> jelmer, guess you do a lot of metadata compression...
[00:23] <lifeless> Noldorin: branch only copies referenced history
[00:23] <lifeless> Noldorin: that is very different to repository level gc
[00:23] <lifeless> Noldorin: which has to delete content other concurrent processes may be looking at
[00:24] <lifeless> Noldorin: someone writing gc can of course layer on all the selective-copy work that branch layers on too.
[01:41] <Noldorin> eek
[01:41] <Noldorin> okay
[01:42] <Noldorin> lifeless, has any of the implementation vaguely described in doc/develoeprs/gc.txt been started in fact?
[01:52] <lifeless> Noldorin: I don't know, sorry - I haven't been following bzr dev closely for oh 3 years now
[01:52] <Noldorin> ah
[01:52] <lifeless> Noldorin: it's not conceptually hard to do
[01:52] <fullermd> Only thing I ever even heard rumors of was that old gc plugin, and if it's even available anywhere it was so long ago that it probably wouldn't fit without substantial rework anyway.
[01:52] <lifeless> Noldorin: but it does involve working at core levels of data storage to ensure correctness around locking / visibility etc
[01:53] <Noldorin> lifeless, yeah, i wouldn't know where to begin with that...
[02:08] <Noldorin> lifeless, fullermd, probably infeasible for someone who doesn't know the internal structure of bzr still, no?
[02:11] <fullermd> Structure is an illusion.
[06:44] <mathrick> jelmer: it just thinks there were no changes
[06:44] <mathrick> mathrick@megumi ~/elisp/dist/git/multiple-cursors $ bzr diff -c -1
[06:44] <mathrick> mathrick@megumi ~/elisp/dist/git/multiple-cursors $
[15:47] <Noldorin> hey fullermd
[15:47] <Noldorin> (if you're there)
[16:41] <Noldorin> lifeless, jelmer ?
[16:44] <mgz> Noldorin: it's a rle of irc, to just ask your question, rather than trying to handshake specific people
[16:44] <Noldorin> mgz, no. i need specific expertise
[16:45] <Noldorin> mgz, and i know who dealt with these things
[16:45] <mgz> the the mailinglist is a better venue. it's the middle of the night in nz for instance
[16:45] <mgz> *then the
[16:47] <Noldorin> ah yes
[16:47] <Noldorin> maybe
[16:58] <mathrick> Noldorin: it's still a better idea to ask directly, even if you ping specific people, to bootstrap the talk, rather than going "you here?" "Yeah, what's up?" "Oh, I was away still around?"
[17:02] <Noldorin> actually, i do have a general question anyway:
[17:02] <Noldorin> what's the best way to learn about the internal structure of bzr?
[17:02] <Noldorin> the way it uses metadata
[17:03] <Noldorin> the formats utilised
[17:03] <Noldorin> etc.
[17:03] <mathrick> Noldorin: for some things, there will be blueprints and design docs on the wiki and launchpad
[17:04] <Noldorin> ah
[17:04] <mathrick> but I'm not familiar with any central place which would have complete, current and accurate picture
[17:19] <Noldorin> hmm
[17:19] <Noldorin> guess i'll just browse the wiki then
[17:49] <Noldorin> mathrick, any areas/pages in particular you might be able to point me to? :)
[17:49] <Noldorin> mathrick, i want to work on a gc/cleanup implementation after i familiarise myself with things
[17:51] <mathrick> Noldorin: nope, sorry, I can't claim anything resembling enough familiarity to be able to tutor people
[17:52] <Noldorin> fair enough
[17:58] <vila> Noldorin: use the source, that's the only up-to-date version. The tests though should give you examples for anything you may dream about ;)
[20:17] <mathrick> vila: what I always find tricky in large systems with involved and tricky design like bzr is finding out why things are, and which parts are the important bits you need to undertsand, and which are just details
[20:18] <mathrick> unfortunately source usually doesn't tell you that
[20:32] <lifeless> Noldorin: the code
[20:32] <lifeless> Noldorin: there are design docs in the source tree; and there are design docs in the classes
[20:33] <jelmer> Noldorin: hi
[23:25] <Noldorin> lifeless, in the classes?
[23:50] <Noldorin> lifeless in the actual code you mean?