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