[03:52] <Peng> Mode +t anyone?
[04:01] <Nafallo> yes, please.
[04:01] <lifeless> what does that do ?
[04:03] <Peng> lifeless: Stops random people like me from being able to change the topic.
[04:04] <Nafallo> lifeless: only ops change topic :-)
[04:10] <lifeless> hmm, I think its fine at the moment
[04:10] <lifeless> if we have trouble we can lock it down, but why do that unnecessarily
[04:13] <Peng> You don't let anyone push to bazaar-vcs.org, do you?
[04:13]  * Peng shrugs.
[04:14] <Peng> Not that IRC topics are quite the same security-wise.
[06:34] <lifeless> Peng: for starters, irc topics are not executable code
[06:36] <Kamping_Kaiser> its easy to fix the /topic
[06:53] <Peng> True and true.
[06:53]  * Peng shrugs.
[06:54] <Peng> It's insecure (by definition), and uncommon.
[07:58] <fullermd> lifeless: Don't *SAY* that!  Now Microsoft is gonna go write an IRC client that auto-executes topics...
[07:59] <fullermd> Remember back when you could say without a trace of irony "Look, email is just text; you can't get a computer virus from an email."
[08:04] <lifeless> fullermd: you can't ... on linux :)
[12:45] <phanatic> hey, is pyrex needed only on build time, or during run time as well?
[12:45] <dato> phanatic: run time, certainly not
[12:45] <dato> phanatic: build time, only if you modify the .pyx files, or you run from bzr.dev, since the tarballs ship a .c version
[12:46] <phanatic> dato: i'm building from bzr.dev. thanks for the help!
[12:49] <phanatic> currently i'm working on a bazaar package for mac. current progress: http://phanatic.hu/bzr/mac/bazaar-dmg-prototype.png
[13:43] <Discpile> hi... i've been wondering about dvcs... and I'm not quite sure I understand something
[13:43] <Discpile> let's say I want to get the latest copy of a repository to my computer (a checkout), how would that work?
[13:43] <Discpile> if there's no centralized repo to get it from
[13:44] <luks> "the latest copy of a repository" -- that means there is *a* repository
[13:45] <dato> Discpile: well, normally projects will say, "this one is the main/master/central copy", and then people can make as many copies of it as they want
[13:46] <Discpile> ah k that makes sense
[13:47] <Discpile> so would a bzr commit push changes to that copy like with e.g. svn?
[13:47] <Discpile> if so, that doesn't sound very decentralized :p
[13:48] <dato> Discpile: by default, no. but bzr allows you to configure it that way (like svn) if you wish. or switch between the two.
[13:49] <Discpile> so normally when I commit... nothing happens? if just the local copy is updated, why even commit? :p
[13:49] <luks> normally when you commit, you commit to your local branch
[13:50] <luks> and later you might either push those changes to a remote branch, send them by mail, etc.
[14:56] <vila> test suite reached the 10.000 tests mark ;-)
[15:47] <lera_zed> hi - how can i check what commits would be pushed into specific branch  ?
[15:48] <dato> lera_zed: bzr missing --mine-only <other_branch_url>
[15:48] <lera_zed> dato: thanks
[15:57] <lera_zed> is it possible to have an alias for branch ?
[15:57] <lera_zed> i mean the actual names are rather long
[15:58] <dato> lera_zed: I don't think so. *but*, I think luks wrote a bookmarks plugin
[15:58] <lera_zed> thanks
[15:58] <dato> lucas, I mean; not sure if luks here is lucas :)
[15:59] <luks> he is, but he also doesn't know if he still has the plugin code :)
[15:59] <dato> https://code.launchpad.net/~luks/+junk/bzr-bookmarks
[15:59] <luks> oh
[16:01] <dato> lera_zed: ^
[16:03] <Verterok> lera_zed: for the hostname part, in *nix you can use .ssh_config to set an alias for it (don't known about win32)
[16:39] <toed> is there no way to checkout without leaving a message?
[17:00] <abentley> toed: You can always checkout without leaving a message.
[17:01] <toed> commit, sorry
[17:02] <dato> toed: I use commit -m '[no message]' :)
[17:02] <toed> so many excess keystrokes!
[17:04] <abentley> toed: commit -m "" works fine.
[17:05] <abentley> Not that I particularly recommend it.
[17:05] <abentley> Oh, my bad.
[17:05] <abentley> There was talk of fixing it.  I thought it had already happened.
[17:07] <abentley> But If you can't tell which revision is which, why use a vcs at all?
[17:08] <frsk> I get a deja vu feeling right now. Wasn't empty commit messages discussed on the mailing list recently?
[17:08] <quicksilver> toed: it's not very hard to set up a shell alias for commit -m '[no message given]'
[17:08] <quicksilver> toed: or a shell script, if that's more to your taste
[17:08] <quicksilver> but, I can't imagine why you'd want to?
[17:09] <dato> quicksilver: a normal bzr alias would do, I have one.
[17:09] <quicksilver> or that!
[17:10] <quicksilver> so many choices of indirection :)
[17:14] <toed> well I'm the only contributor so I thought there was no point leaving a message
[17:14] <toed> but on reflection you're right, it's probably helpful
[17:15] <dato> toed: *very*
[17:20] <quicksilver> I leave brief messages on my commits even on personal projects
[17:20] <quicksilver> "implemented network support"
[17:20] <quicksilver> "changed gui to use more colors"
[17:20] <quicksilver> nothing details, just enough to remind me!
[17:20] <quicksilver> as I rule I always quickly review the diff before committing
[17:20] <quicksilver> (C-x V = before C-x V c!)
[17:21] <dato> quicksilver: I always catch *something* in the last minute review ;)
[17:21] <quicksilver> yes, I often do
[17:21] <quicksilver> It's a useful catch
[20:01] <dato> jelmer: rebase uploaded
[20:01] <artooro> hey folks, haven't been able to find this information so thought I'd ask here, is there a limitation to the size of file I can commit?
[20:02] <jelmer> dato: thanks!
[20:02] <dato> np; leaving now.
[20:02] <artooro> I'm trying to commit a 4.1GB file and it's failng
[20:02] <beuno> artooro, the limitation is the amount of RAM you have
[20:02] <artooro> ok
[20:02] <Discpile> sounds like you should FTP stuff of that size :p
[20:02] <artooro> so I guess you guys and git are in the same boat there then :)
[20:03] <artooro> no actually I want to backup revisions
[20:03] <artooro> no network involved here
[20:03] <beuno> artooro, it's a tricky one, yes
[20:03] <Discpile> why not split the file into more handy bits? :o
[20:03] <beuno> might be solved in the future
[20:04] <artooro> yeah, alright.
[20:04] <jelmer> artooro: nothing should prevent us from doing that, except the focus of development has been on other things
[20:04] <artooro> that's totally understandable