[00:02] <jelmer> schierbeck: yes, though I can try to change that
[00:05] <schierbeck> that would be great -- i have a one-line patch that fixes a crasher in the mainline version of the viz
[00:06] <schierbeck> i'm not sure if it needs to go through the review process -- even if it doesn't, i'm not able to push
[00:07] <jelmer> schierbeck: ok, it's now at ~bzr-gtk/bzr-gtk/trunk
[00:07] <schierbeck> wow, that was fast
[00:07] <schierbeck> do you think i should push the revision?
[00:07] <schierbeck> it's just removing an import of a now nonexisting file
[00:08] <jelmer> yeah, sounds good to push without review
[00:08] <jelmer> so now the main branch is at ~bzr-gtk/bzr-gtk/trunk you could start pushing your own approved revs :-)
[00:09] <schierbeck> nice :)
[00:11] <Peng> What order are the sections ("BUG FIXES", "IMPROVEMENTS", etc.) in NEWS in?
[00:17] <Odd_Bloke> Peng: I'd suggest looking at NEWS to find out. :p
[00:19] <GuyIncognito> Newbie question:  I'm working on a project with the "Decentralized with shared mainline" workflow.  I want to "fork" the project into two different development efforts.  I guess this would be "making a new revision"?  But what is going to happen when people start pushing their changes back to the mainline from the two different branches?  Is there a best practises for this, or am I going about it the wrong way?
[00:20] <GuyIncognito> * sorry I meant to say "This would be 'making a new branch'?"
[00:21] <Odd_Bloke> GuyIncognito: What you would do is 'branch' the shared mainline into a separate branch.  You would then 'merge' changes from that branch back into the mainline.
[00:23] <GuyIncognito> Old_Bloke:  OK.  What happens if several people want to work on the new branch?
[00:23] <Peng> Odd_Bloke: Seems to be arbitrary.
[00:26] <fullermd> GuyIncognito: You can have multiple shared branches, instead of just one.  Just set up the second similar to the first.
[00:27] <Odd_Bloke> GuyIncognito: Well, any given branch can be treated as centralised.  That is to say you could branch 'mainline' to 'feature-1' and then have people use 'feature-1' using any of the listed workflows.
[00:27]  * Peng adds a reference to the bzr branch to the trivial bug he's been working on. :O
[00:28] <Peng> I feel kinda bad about polluting the big important list of branches with something trivial.
[00:28] <Peng> But it also has taken a few commits and continued to be modified, at least a little.
[00:32] <GuyIncognito> fullermd, Odd_Bloke:  Thanks!
[00:32] <Odd_Bloke> GuyIncognito: No worries. :)
[01:08] <JordanC> Hyello
[01:09] <JordanC> Does anyone else have problems with Launchpad & olive?
[01:09] <JordanC> I try to grab from there or push and I get "unexpected response"
[01:10] <abentley> The location for bzr-gtk has just moved to ~bzr-gtk/bzr-gtk/trunk
[01:10] <JordanC> ?
[01:12] <abentley> ?
[01:12] <JordanC> Were you talking to me?
[01:13] <abentley> Yes.  I thought that might be relevant to you.
[01:14] <JordanC> Hmm
[01:14] <JordanC> Still wondering why no SVN on launchpad :P
[01:15] <abentley> Still wondering why no SVN on list of "once-popular products that no one's using"
[01:16] <JordanC> ...no-one's using SVN?
[01:16] <abentley> No one should be.
[01:16] <JordanC> (I know of at least 30 off the top of my head)
[01:16] <JordanC> Well, i've had nothing but problems with bazaar -_-
[01:17] <abentley> I'm sorry to hear that.
[01:18] <fullermd> It probably saw svn installed on the system and got huffy.
[01:18] <abentley> So what protocol are you using to retrieve bzr-gtk?
[01:19] <JordanC> I'm trying to use olive at the mo
[01:19] <abentley> Same source tree.
[01:19] <JordanC> Can i get bzr-gtk via yum
[01:21] <abentley> No idea.  The Bazaar project has debs, but I don't think any rpms.
[01:21] <JordanC> Yeah, I have it
[01:21] <JordanC> But there's no GUI
[01:21] <JordanC> It's just tools
[01:21] <JordanC> And I'm using KDE :P
[01:22] <JordanC> bzr-gtk is a plugin for Bazaar that aims to provide GTK+ interfaces to most Bazaar operations.
[01:22] <fullermd> Can probably do a quick grep through yum list (or is it yum search?  I can't remember) to see if it's in its standard repo.
[01:22] <abentley> The Bazaar project has debs FOR BZR-GTK, but I don't think any rpms.
[01:23] <JordanC> Well, no app is shown
[01:23] <JordanC> lessee
[01:23] <abentley> I know what bzr-gtk is.  I am one of the contributors.
[01:23] <fullermd> If it's not in the 'official' yum db, I haven't heard of anywhere else offering RPMs (which doesn't mean much since I don't track that, but...)
[01:25] <JordanC> Oh dude
[01:25] <fullermd> If it's not there, it's probably easiest (for experimenting, anyway) to just grab a copy manually and stick it in your personal plugins dir.
[01:25] <JordanC> Now I have to install nautilus
[01:25] <JordanC> No way am I using bazaar
[01:25] <JordanC> :X
[01:25] <fullermd> You don't have to for bzr-gtk itself; some package may be listed with it.  I sure don't have nautilus around.
[01:25] <abentley> Nautilus is not a hard dependency of bzr-gtk.
[01:26] <JordanC> Man, good
[01:26] <JordanC> Cause it's nowhere near as good as Konqi :/
[01:26] <JordanC> Anyhow
[01:26] <fullermd> Is that some new-fangled version of 'ls'?   ;p
[01:26] <JordanC> What is just, the long and short of it -- how do I make it easier just to commit without having to fanny around? :P
[01:27] <JordanC> It's getting annoying when there's GUI's that don't work and bazaar is similar to arch
[01:27] <abentley> I'm not sure what you mean about guis that don't work.
[01:27] <JordanC> Olive doesn't work
[01:27] <fullermd> That's a bit off my turf.  I always just use the CLI; only thing I generally use -gtk for is an occasional viz.
[01:27] <JordanC> Won't let me commit, won't let me pull
[01:28] <JordanC> Can't connect to servers
[01:29] <abentley> Well, commit works for me.
[01:29] <JordanC> Using olive?
[01:29] <JordanC> Okay, well if this is the case maybe I'm not getting the connection URL's correct
[01:29] <fullermd> You'd probably have to be a little more specific about what you're trying to commit/pull and what servers   :p
[01:29] <JordanC> What's the actual URL you need to specify
[01:29] <JordanC> My project on launchpad is photoncrm
[01:30] <JordanC> And the advised path is ~jordancdarwin/photoncrm/modules/
[01:30] <abentley> JordanC: yes, using olive.
[01:30] <Odd_Bloke> So 'bzr+ssh://jordancdarwin@bazaar.launchpad.net/~jordancdarwin/photoncrm/modules/' for pushing.
[01:30] <Odd_Bloke> JordanC: ^
[01:31] <fullermd> For writing it, I think it would be something like bzr+...   what Odd_Bloke said.
[01:31] <JordanC> Still
[01:31] <JordanC> When I use that, I get "Cannot read response from server"
[01:31] <JordanC> And for pulling?
[01:32] <fullermd> Mmm.  I get a bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~jordancdarwin/photoncrm/modules/" when I try branching it.
[01:32] <JordanC> bzr push bzr+ssh://jordancdarwin@bazaar.launchpad.net/~jordancdarwin/photoncrm/modules
[01:32] <JordanC> That's what I get given
[01:33] <JordanC> Haha
[01:33] <JordanC> Yeah, it just crashed
[01:33] <abentley> Well, it looks like there really is no branch there.
[01:34] <JordanC> " This branch has not been published yet."
[01:34] <fullermd> So LP has the branch listed, but not really there.  I don't know LP well enough to know how you do that, or fix it.
[01:34] <fullermd> I've never created a LP branch except by pushing it.
[01:35] <JordanC> Why is it that after some errors, GTK will actually not allow me to click buttons, but use the keyboard instead? Argh, frustrating
[01:35] <JordanC> Hmm
[01:35] <JordanC> Unsupported protocol for url "bzr push bzr+ssh://jordancdarwin@bazaar.launchpad.net/~jordancdarwin/photoncrm/modules"
[01:35] <JordanC> Everything is fine
[01:36] <JordanC> Hang on
[01:36] <JordanC> Why is it pasting that
[01:36] <JordanC> Okay, here we are
[01:36] <JordanC> Unknown error
[01:37] <JordanC> end of file reading from server.
[01:37] <JordanC> :)
[01:37] <abentley> The bzr+ssh protocol has poor diagnostics.
[01:37] <abentley> Try using sftp instead.
[01:37] <JordanC> In olive?
[01:37] <abentley> Sure.
[01:38] <JordanC> Same error
[01:38] <abentley> Just switch sft for bzr+ssh in the URL.
[01:38] <JordanC> Yeah, I know how to do it ;-)
[01:38] <abentley> Sorry "sftp".
[01:39] <abentley> Okay, can you log into launchpad?
[01:39] <JordanC> Already done
[01:39] <abentley> e.g. using an sftp client?
[01:39] <JordanC> Yes
[01:40] <JordanC> Works fine
[01:41] <abentley> And you're using the same user-id?
[01:42] <JordanC> yup
[01:43] <abentley> Sound like you need to talk to someone in #launchpad, then.
[03:25] <bialix> jam: ping
[04:11] <gdoubleu> I can't remember, bzr branch lp:/// support is in bzr proper correct?  Not bzrtools?
[04:13] <fullermd> gdoubleu: Technically, I think it's in the launchpad plugin, but that's shipped with bzr.
[09:12] <imbrandon> anyone got any clues on this error ( trying to use bzr-svn )
[09:12] <imbrandon> http://paste.ubuntu.com/2392/
[09:12] <imbrandon> *hopes some is awake at this hour*
[09:13] <AfC> imbrandon: Upgrade to >= 0.92 and try again
[09:13] <AfC> imbrandon: (1.0rc1 would be better)
[09:14] <imbrandon> AfC: ok , is it in hardy or do i need to compile
[09:14] <imbrandon> i'm running gutsy with all -backports/-updates
[09:15] <AfC> imbrandon: I haven't the faintest idea what a gutsy, hardy, or whingy are, but if you look on the Bazaar website you'll find that they have an apt repo that Debian derived distributions can use.
[09:15] <imbrandon> AfC: rockin ok, ( fwiw they are the ubuntu codenames )
[09:16] <imbrandon> gutys being the latest stable , anyhow thanks, i'll try that
[09:16] <imbrandon> gutsy*
[09:18]  * AfC is heaping scorn on the idea a) of codenames, and b) that Debian and Ubuntu people seem to expect that anyone else would have the faintest fucking clue what the hell they are talking about
[09:19] <imbrandon> no i dident *expect* you to know, sorry for the assumtion, bzr being another canonical project i assumed the right hand would know about the left hand, but assuming makes an ass+u+me , wont happen again
[09:24] <AfC> Anyway, 0.93 ^W 1.0rc1 is just out, and you'll probably do well to give it a try as it's 3-4 months (and 3-4 releases) newer than what you were using. The Bazaar hackers continue to move at an astonishing rate and problems encountered in a version that's that old are likely long since resolved.
[09:27] <imbrandon> k
[09:48] <JordanC> Hey dudes
[09:48] <JordanC> :)
[09:51] <imbrandon> ello JordanC
[11:25] <dato> siretart: so, as a person who's fought with Recommends... ;) what's your opinion on having bzr recommend: bzrtools, and suggest: bzr-gtk, bzr-svn
[11:25] <dato> siretart: I think bzrtools is on the verge of not being appropriate for recommends, but only on the verge :)
[11:27] <siretart> dato: I would argue this way:
[11:27] <siretart> dato: would you expect a typical bzr user to also install bzrtools?
[11:27] <siretart> if yes -> recommends, if no ->suggest
[11:28] <siretart> (I'd vote in favor of it)
[11:29] <dato> yeah, me too. I think it'd be useful for it to be available by default.
[11:29] <dato> I'm also revamping the description.
[11:29] <siretart> great, thanks
[11:33] <dato> jam, vila: I would also like to know whether you think python-pycurl should still be pulled by default when installing bzr (in Debian, and possibly in ubuntu), or it's better to leave it out now.
[11:38] <dato> siretart: do you have any idea why on earth we Suggest: libxml2-utils?
[11:38] <siretart> dato: no idea. maybe lifeless knows?
[11:39] <dato> maybe. the changelog is not helping.
[11:40] <james_w> /usr/bin/xmllint, /usr/bin/xmlcatalog
[11:40] <james_w> I'm not sure what either of those would be for.
[11:40] <james_w> hi all btw.
[11:40] <dato> hi james_w
[11:48] <dato> oh, no jelmer
[12:13] <dato> siretart: http://dpaste.com/26427/
[12:16] <james_w> dato: conclicts
[12:17] <james_w> "yet able to adapt to many workflows, reliable, and easily extendable." is a little uncomfortable, I would suggest dropping the "yet".
[12:43] <dato> james_w, thanks, fixed (both).
[12:44] <james_w> dato: it's good, thanks for doing it.
[12:46] <vila> "no special software the server is needed" ? "no special software is needed on the server"
[12:47] <dato> the intention was "no special software *in* the server is needed"
[12:47] <vila> regarding pycurl, there are two http implementations in bzr: one based on pycurl, the other on urllib
[12:48] <dato> yes
[12:48] <vila> if pycrul is the default if present
[12:48] <dato> yeah, I know.
[12:48] <vila> the major difference is that pycurl verifies ssl certificates
[12:48] <dato> the question was, whether to make installing bzr in a system also pull pycurl in
[12:48] <dato> iow, what do you feel that would be a better default: pycurl available or not
[12:49] <james_w> dato: I would think available.
[12:49] <vila> dato: I'm a bit biased since I rewrote most of the urllib ;)
[12:49] <james_w> also looking again I think vila's "no special software is needed on the server" is better.
[12:50] <dato> ok, done
[12:52] <vila> frankly I don't know if pycurl should be pulled or not. When people want certificate verification pycurl is mandatory (today), if they don't want certificate verification pycurl should be avoided (by forcing the use of  urllib)
[12:52] <james_w> of course the best solution would be to get vila enough spare time to add certificate validation to urllib.
[12:52] <dato> vila: avoided?
[12:53] <vila> james_w: ;-)
[12:53] <james_w> yeah, pycurl wont let you access a site with a self-signed certificate for instance, so you have to force urllib to access it.
[12:53] <vila> dato: no hhtps connection can be issued if certificate verification fails (included self-signed certificates)
[12:54] <vila> and also if your installation is screwed or the site use an unknown CA
[12:54] <vila> since urllib makes no verification... it's usable. *And* I will provide the necessary hooks to allow urllib to cope with the situations above
[12:55] <dato> so, maybe not pull pycurl, and leave a note in README.Debian on when it could be useful?
[12:55] <dato> maybe downgrade it to suggests
[12:55] <dato> ah, I meant to mention in the description what paramiko is useful for
[12:55] <vila> you stop doing that ?
[12:56] <vila> put it back and add an equivalent section for pycurl maybe ?
[12:56] <dato> stop doing what? there was never any place in the debian packagin explaining what was paramiko needed for
[12:56] <vila> s/if your installation is screwed/& regarding the certificates/
[12:57] <vila> I heard at least two reports (or three) where the ca-certificates package were not installed even when pycurl was (or liburl, or curl, whatever ;)
[12:58] <vila> s/liburl/libcurl/
[13:00] <vila> err, waitaminute, james_w, *you* had a case where ca-certificates not installed no >
[13:00] <vila> s/>/?/
[13:01] <james_w> vila: yeah, I've tried to see why, but I'm couldn't see it.
[13:01] <vila> dato: sry, misunderstood you, I thought you said you *was* doing, I think it will be a good idead to do so.
[13:02] <vila> james_w: I think I sent you an email afterwards with some hints (after looking a bit myself)
[13:02] <vila> Subject: ca-certificates as a bzr dependency
[13:02] <vila> To: James Westby <jw+debian@jameswestby.net>
[13:02] <vila> Date: Wed, 21 Nov 2007 12:01:48 +0100
[13:02] <james_w> vila: yeah, thanks.
[13:02] <vila> AAARGH silly posting addresses here :-(
[13:03] <vila> so sorry :(
[13:03] <dato> is paramiko needed to push over bzr+ssh?
[13:04] <james_w> vila: no problem, there are plenty of other places to harvest it.
[13:04] <james_w> and the '+' is a good anti-spam device anyway.
[13:05] <vila> really ? I was wondering about that cause my spam level have never been too high and I tend to always use + addresses
[13:06] <vila> dato: checking...
[13:07] <vila> dato: yes it is
[13:07] <dato> thanks
[13:07] <dato> bbiab
[13:07] <dato> (maybe it'd should be a dependency then)
[13:07] <dato> bbiab
[13:07] <james_w> vila: my MTA's logs show loads of rejects to debian@jameswestby.net, which I think is a great help.
[13:09] <vila> amazing... I thought there were clever enough to include + as a valid component... or may be the clever ones think that people using + are naturally anti-spam ;-)
[13:10] <vila> regarding urllib's certificate verification, I have a branch whith an https test server using the ssl module provided by python2.6 (after  dirty port of bzr to python2.6)
[13:12] <vila> this branch is on the back burner for now because that module is currently under work in 2.6, 3k and as a package for py2.3->2.5, so it's bit hard to find the right version ;-)
[13:12] <vila> 2.6, 3k and the package being at different levels last time I checked...
[13:14] <james_w> vila: apparently 0% of my current spam folder (1700 messages) is to that address, > 90% of ham is to that address.
[13:14] <james_w> do other countries have the real SPAM, i.e. the meat product?
[13:15] <vila> Not that I know of ;-)
[13:16] <james_w> ah, you're missing out.
[14:11] <abentley> vila: What's it used or?  The ssh connection can be through openssh, and the protocol is our own.
[14:33] <vila> abentley: try:
[14:33] <vila>     from bzrlib.transport import ssh
[14:33] <vila> except errors.ParamikoNotPresent:
[14:33] <vila>     # no paramiko.  SmartSSHClientMedium will break.
[14:33] <vila>     pass
[14:33] <vila> in smart/medium.py
[14:34] <vila> ?
[14:34] <abentley> Perhaps it's used for something, but I would have thought not.
[14:35] <vila> me too, that's why I checked, I'm as surprised as you, may well be a bug
[14:37] <abentley> I guess we'll just have to harass spiv.
[14:38] <vila> spiv: ^
[16:51] <ubotu> New bug: #173274 in bzr "Allow pre-export hooks" [Undecided,New] https://launchpad.net/bugs/173274
[16:58] <jelmer> abentley: your announcement of bzrtools 1.0 doesn't mention switch being merged into core. Did it make it into 1.0rc1?
[16:59] <abentley> Actually, I did mention switch.
[16:59] <abentley> Oh, drat.
[16:59] <abentley> I meant "switch", not "shelf".
[17:01] <abentley> Okay, I've fired off a correction.
[17:03] <jelmer> ah, that explains it :-)
[17:19] <Peng> Huh. Now that I'm using bzr.dev, I don't want to bother installing 1.0rc1.
[17:25] <abentley> Yeah, I'm chronic that way.
[17:26] <abentley> I did have to revert to 1.0rc1 temporarily, to make sure bzrtools 1.0.0 works with it.
[17:29] <abentley> Which you can do with "bzr revert -r branch:http://bazaar-vcs.org/bzr/bzr.1.0/"
[17:30] <Peng> What the hell is wrong with Firefox? It refuses to download GPG signatures. /me wgets the bzrtools .sig file.
[17:32] <jelmer> so why's bzr.dev still claiming it's 0.93 ? shouldn't that be 1.0.1 ?
[17:34] <Peng> NEWS was updated but I guess nobody got around to updating the version number.
[17:35] <Peng> And now they're off for the weekend?
[17:41] <Peng> Going from an installed copy of 0.92 to 1.0rc1 is a 291 KB pack. :)
[18:04] <Peng> Hm, it's not possible to branch a dirstate branch into an (empty) pack repo?
[18:04] <Peng> Oh, never mind.
[18:05] <Peng> dirstate-with-subtree.
[18:05] <Peng> Yes, "KnitRepository" is super-useful information.
[18:09] <Peng> jelmer or something: Who runs doc.bazaar-vcs.org? The docs need to be updated. 1.0rc1 links to packrepo.html but it's still a 404.
[18:19] <james_w> Peng: I think one of poolie, jam or lifeless should be able to update it.
[18:21] <Peng> Okay.
[18:22] <Peng> jam or lifeless or someone: http://doc.bazaar-vcs.org/latest/developers/ needs to be rebuilt. 1.0rc1's "help formats" links to packrepo.html, but it's still knitpack.html on the server. It would also be nice if there was a 301 redirect from knitpack.html to packrepo.html.
[18:28] <Peng> Am I still connected?
[18:28] <dato> jelmer: re REJECT, possibly the XS-* field has to be installed in the archive, not only in incoming, for it to work; so try again tomorrow
[18:28] <james_w> Peng: no :)
[18:28] <Peng> That was weird.
[18:29] <Peng> I lost my connection to the Internet, but the DSL light on the modem was still on. Then while I'm reconnecting to all the IRC networks, the last one, Freenode, recovers.
[18:29] <Peng> Weird.
[18:30] <Nafallo> not really...
[18:30] <Peng> Yes it is.
[18:30] <Nafallo> why?
[18:30] <Peng> How can I get disconnected without either the modem or computer being aware of it?
[18:30] <Nafallo> did you get a new IP?
[18:30] <Nafallo> ah
[18:30] <Peng> Nafallo: Nope. But since my account was shuffled around, I've stopped getting new IPs anyway.
[18:31] <Peng> (The one time it's gone down since it was shuffled, anyway.)
[18:32] <Nafallo> well, your PPPoE can disco without line-sync go down, and your computer is only aware of connectivity to the modem.
[18:32] <Nafallo> as far as freenode go, you never reached the TCP timeout.
[18:33] <Peng> Not PPPoE anymore. "ENET ENCAP".
[18:33] <Peng> My hostname changed from saying "dyn" to "dhcp" and now I get crappier IPs.
[18:34] <Nafallo> nice :-)
[18:41] <Peng> I got a new modem too, because apparently mine should've burned out years ago. I'm still using the old one because I don't want the (minor) downtime. I was just about to switch it out before the connection started working again.
[18:41] <Peng> Anyway, back on topic. Not like anything's happening...
[19:25] <dato> jelmer: ping
[19:33] <sommer> hello, I checked out the ubuntu-hardy docs branch from LP... I then changed my "name" and "Display Name" in LP and I can no longer commit
[19:34] <sommer> I think the local version is still using the old name
[19:34] <sommer> is there a way to change that without re-downloading?
[19:34] <lifeless> Peng: which branch? the one took to hg? basically I'd like to know how we compare
[19:34] <lifeless> Peng: are we still so slow you would have moved?
[19:35] <Peng> lifeless: Can you rebuild the docs? Or poke someone who can?
[19:35] <lifeless> I'll see what I can do
[19:36] <Peng> Thanks.
[19:36] <james_w> sommer: you probably want to use 'bzr bind' with your new username in the URL.
[19:36] <sommer> james_w: ah... I'll try that
[19:36] <Peng> Let's see how long it takes to extract a 1.3 GB .tar.
[19:37] <lifeless> Peng: obviously for these tests I want you to upgrade the branch to packs
[19:38] <Peng> 1 minute and 3 seconds!
[19:38] <sommer> james_w: genius that worked.  Thank you very much
[19:39] <Peng> Hmm. I had like 8 copies of the data, and removed all of it except for 1 copy (well, there are still 2 copies of the bzr repo), and it looks like I took the copy I was experimenting with with it.
[19:39] <Peng> What makes something a shared repo vs. a non-shared repo? The presence of a branch in the same dir?
[19:39] <lifeless> .bzr/repository/shared-storage
[19:40] <Peng> Ah.
[19:40] <Peng> Bah, should've just checked.
[19:41] <Peng> Now, let's see how long it takes to convert to packs.
[19:42] <Peng> (even worse, pull into a new branch, building a new working tree)
[19:42] <Peng> Think I have time to brush my teeth?
[19:42] <Peng> Well, let's see if I can brush my teeth in time, then!
[19:42] <Peng> BRB.
[19:46] <Peng> Hmm. It might work well to use git for ~/local instead of bzr. Since it doesn't track renames, I don't have to try to.
[19:47] <Peng> Wait, I do like being able to do renames, though.
[19:47] <lifeless> rofl
[19:48] <Peng> I like being able to do renames when I want to, but I don't want to have to think about them when I don't.
[19:49] <lifeless> commit --automatic is what you want
[19:49] <lifeless> as we delete automatically today
[19:49] <lifeless> you can do:
[19:49] <lifeless> bzr add; bzr commit;
[19:49] <lifeless> and you'll get a new snapshot
[19:49] <lifeless> no thought.
[19:55] <Peng> Oh, gosh. It only took 9 minutes.
[19:56] <Peng> Now, why am I swapping so badly?
[19:58] <Peng> Better now. I guess bzr had just used a lot of RAM.
[20:08] <Peng> lifeless: Wow. 17 seconds user time. Slightly higher sys than with hg, I think. :P
[20:09] <Peng> lifeless: Now, it's gotten larger since this old copy was made, so it would be slower (no idea how much), but if bzr was this fast in August, I never would've switched to hg.
[20:09]  * Peng wanders off. Star Trek.
[20:35] <lifeless> Peng: cool
[20:37] <lifeless> Peng: btw, histor shouldn'y slow it down noticably for commits anymore, only total count of files/size of changed files.
[21:34] <Peng> lifeless: Cool!
[21:35] <Peng> lifeless: Same with hg.
[21:38] <Peng> Meh. The problem with me is also that the files I'm committing keep getting larger, so even if history doesn't slow it down, the diffs will.
[21:49]  * Peng wanders off.
[22:28] <dato> jelmer: btw, you were the second approver of my small patch to NEWS, maybe you could merge it? http://bundlebuggy.aaronbentley.com/request/<20071129185051.GA12330%40chistera.yi.org>
[23:29] <abentley> lifeless: ping