=== BasicMac is now known as BasicOSX === n2diy_ is now known as n2diy [09:28] <``Cube> jelmer: the icons are ready! [09:28] <``Cube> I updated them! [09:28] <``Cube> and all sizes [09:28] <``Cube> 192x192, 144x149, 48x48, 32x32, 22x22 and 16x16 [09:30] <``Cube> also, I doesn't seems like I got your cc [09:57] <``Cube> jelmer?? [11:15] <``Cube> jelmer? [11:16] ``Cube: Hi! [11:16] <``Cube> hey [11:16] <``Cube> did you get the link, jelmer? [11:16] <``Cube> uh [11:16] ``Cube: No [11:17] <``Cube> jelmer: I mean did you get my last messages [11:17] <``Cube> well [11:17] <``Cube> http://cubibubi.cu.funpic.de/tango/bazaar/ [11:17] <``Cube> check this out [11:18] <``Cube> I fixed the issue you told me yesterday [11:18] ``Cube: thx [11:18] <``Cube> and? [11:18] <``Cube> how do you like themß [11:18] <``Cube> ? [11:19] ah [11:19] yep, this is what I meant [11:19] brb [11:19] <``Cube> I didn't get the mail you wanted to cc me? [11:19] <``Cube> ! [11:21] <``Cube> oh ok, I got it :P [11:22] <``Cube> jelmer: but it would be nice if you used my real name instead of that nick [11:46] re [11:46] ``Cube: I didn't know your real name, that's why I used your nick [11:46] <``Cube> sure of course! [11:46] <``Cube> no problem, just for the next time [11:50] ``Cube: sure, will do [11:50] ``Cube: Btw, nice work on the icons. I like them (-: [11:50] <``Cube> jelmer: thanks. what do you think, will they become official? [11:51] ``Cube: It would be nice to get some input from the other bzr-gtk team members [11:52] <``Cube> jelmer: hmm yes, you're right [11:53] <``Cube> just subscribed to the list [12:02] <``Cube> jelmer: you might send the pictures I did attached or just send the link to the mailing list for the people to get a general idea and to be able to decide whether this is worth consideration or not [12:02] <``Cube> or should I do this? [12:04] <``Cube> jelmer... [12:05] ``Cube: Sorry, I'm usually a bit slow replying on IRC [12:05] ``Cube: Either would be fine with me [12:06] <``Cube> hehe ;) no problem [12:06] <``Cube> you mean, its ok if I do it, but you wouldn't have a problem doing it yourself? [12:06] ``Cube: I'd be happy to send the icons, but it may also be a good way for you to introduce yourself :-) [12:06] yep [12:06] <``Cube> hehe :D exactly what I wrote :P [12:06] <``Cube> ok [12:06] :-) [12:06] yep, whatever you prefer [12:06] <``Cube> ill introduce myself, ok? [12:07] <``Cube> jelmer: can I attach images to the email I send to this mailing list? [12:07] ``Cube: Yep, that's fine [12:09] <``Cube> is there any size restriction? [12:16] Not sure, I think it's a couple of hundred kb [12:16] <``Cube> oh ok [12:17] <``Cube> thanks [12:46] whois ``Cube [12:46] oopsa [12:46] <``Cube> :P [12:46] <``Cube> its me [12:46] :-) [12:46] hadn't seen you here before [12:46] <``Cube> ;) [12:46] <``Cube> yea [12:46] <``Cube> I'm kinda new here [12:47] converting from some other vcs or just thinking? [12:47] <``Cube> huh? [12:48] mlh: ``Cube is helping us (bzr-gtk) out with some icons [12:48] axcellent [12:49] I just 'updated' in fedora7 [12:49] <``Cube> ehm, is there anything else then bzr-gtk here? [12:50] got bzr 1.0, bzr-gtk 0.93 bzrtools 1.0.0 .. good work! [12:51] <``Cube> ah [14:02] <``Cube> anyone got my mail? [14:02] ``Cube: I did [14:03] <``Cube> oh [14:03] none of the other bzr-gtk folks appear to be here atm [14:03] <``Cube> could you reply something? [14:03] <``Cube> hmm ok [14:03] it's usually more busy [14:04] <``Cube> ok ;) === bigdo1 is now known as bigdog [14:30] does pull need a destination? [14:31] aadis, It's usually the present branch. I don't think it even makes sense from outside a branch. [14:31] yeah. all the examples never mention that you have to specify the full path the first time [14:32] I meant, source to pull from [14:32] aadis, And if you don't, the default is the place from which you cloned that branch the first time, yes? (I may be wrong. I'm pretty new to Bzr, but I've used others.) [14:33] i don't think that works. [14:33] i just did a checkout, and then immediately a pull. fails. [14:33] Hmmpf. [14:33] @areia:~/src/pentaur/argus $ bzr pull [14:33] bzr: ERROR: No pull location known or specified. [14:33] if you have a checkout, use 'bzr up' [14:34] the default will be set for branch, not pull [14:34] er, not co [14:35] aadis, Ah, that's it. Don't use "checkout". That's the command for Svn users who don't know any better. [14:36] ...maybe. [14:36] * CardinalFang lurks. [14:36] well, that's what the docs suggest [14:36] for doing distributed development [14:36] since chekcout allows you to do local commits without --local all the time :) [14:37] it's the other way round [14:37] really? [14:37] unless you co from a local repository, then co and branch don't need --local [14:37] er, "local mirror of a remote branch in a local repository" [14:43] ah, ok. so it seems. [14:43] if i create a local branch (ie i have checked out trunk and branch from it) [14:44] how do i ensure my branch also gets committed to the server? (so two people can work on one feature branch) [14:45] you can bind it to the server (cd branchdir ; bzr bind sftp://host/branch) [14:45] then it acts as if you did a co sftp://host/branch [14:46] ah. so when i commit it goes to server. [14:46] as well as the local branch, yeah [14:46] you can "bzr unbind" to disable it [14:53] cool. thanks bob2 [14:53] bob2: and i'm assuming sftp://host/branch already exists? or someone needs to run bzr init for it? [14:55] right [14:56] ok, so someone will need to do "bzr init branch" on host? [14:56] yes [14:57] maybe it works over sftp etc now [14:57] appears to [14:58] we'd be using bzr+ssh anyway, so smart server might be able to do it [15:01] doesn't seem to work for me, over bzr+ssh [15:02] wfm [15:03] @areia:/tmp/sandbox/test-1-branch $ bzr bind sftp://a@pr0n/home/p/bzr/sandbox/test-1-branch [15:03] bzr: ERROR: Not a branch: "sftp://a@pr0n/home/p/bzr/sandbox/test-1-branch/". [15:04] oh bind [15:05] does "ssh a@pr0n ls -la /home/p/bzr/sandbox/test-1-branch/" show a .bzr dir? [15:07] no [15:07] ah, i see your point. I need to do bzr init sftp://a@pr0n/home/p/bzr/sandbox/test-1-branch first [15:08] * aadis is slow today [15:09] though http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#using-checkouts says: [15:10] heh, nice machine name [15:10] it's also cnamed to cocaine.company.com [15:11] and also dev.company.com for the suits ;) [15:14] aadis: not sure if I understand the situation fully, but wouldn't you want to bzr push to the remote location not init it? (unless you havn't created the branch locally yet I guess) [15:14] i'm *very* new to bzr, so i'm trying to figure the right thing [15:15] we're following the distributed model [15:15] so when i'm hacking on a local branch and also want to share it with other people [15:15] ok, that typically means that you have a local branch of the project and then push to a place that other people can pull from manually [15:16] is bzr push the right idea? /home/p/bzr/sandbox was created with "bzr init-repo sandbox" [15:16] though if you have a local server I guess having a bound branch to it works too [15:16] i think we'd do a bind/commit/push/unbind would be done very infrequently [15:17] TFKyle: so should we do a bzr init && bzr bind ; or bzr push? [15:18] aadis: not sure, have you created the repo locally already? [15:18] what do you mean by locally? my machine or the server? [15:18] your machine [15:19] what i did was. bzr init-repo; bzr branch sftp://server/trunk; bzr branch trunk fix-branch [15:19] so i think yeah, the repo is created locally [15:24] ok, and you want to put that branch onto another server? if so then you probably want to bzr push it to that server then optionally bind to the branch on that server (not sure how repos work really though, havn't looked at them much) [15:25] Hi all. I want to write a plugin trigger that runs only for one project. Any suggestions? [15:31] (if you bzr init'd another branch on the server it wouldn't have any commits your local branch has currently) [16:39] TFKyle: ah, i see. good point. [17:08] No one has ideas about making a plugin trigger run for only one kind of project? [17:09] I could insert some sort of test at the beginning, I suppose, and exit if it fails. [17:09] ^exit^return [17:14] Maybe require that a specially-named file exists. What would that be? "if not master.repository.path2id("foo"): return False" [17:23] CardinalFang: sounds like you want a configuration directive [17:24] CardinalFang: branch.get_config().get_user_option("foo") [17:25] CardinalFang: then people can put "foo = whatever" in their ~/.bazaar/locations.conf under the appropriate path [17:35] radix, I have more than a hundred people to give this to. Giving a file is fine. Telling them to customize it is not. [17:35] unfortunately there's not a branch-hosted configuration mechanism yet :\ you could definitely come up with something ad hoc. [18:19] It would be cool and useful to safe the changeset (and file) commit messages saved at "uncommit" and inserted as the default for the next commit. [18:19] ^safe^save [20:32] Would anyone care to look at a design document for a new distribution I am going to make as part of a University project? [20:32] You know, shoot some holes in any of the design/implementation issues that are probably there before I start coding something impossible. [22:02] guys, kind of dumb question but... how do I set the bookmarks in bzr-gtk? [22:02] after a couple of minutes fighting I gave up [22:02] :p