[00:01] <jelmer> maxb: hi
[00:01] <maxb> hello
[00:02] <jelmer> maxb: bzr-notify listens to dbus requests
[00:02] <jelmer> maxb: it doesn't poll by itself, although there was a avahi plugin at one point that could forward commit events between avahi and dbus
[00:02] <maxb> ok, is there something that will poll remote branches and send dbus requests? :-)
[00:02] <jelmer> maxb: there isn't something like that yet afaik
[00:03] <jelmer> the avahi plugin worked well at some point (it was a neat toy to use at sprints to see what other people around you were committing), but I think it's regressed since
[00:03] <jelmer> for non-LAN branches, I don't think there's anything
[00:05] <zsquareplusc> maxb: indirect solution, mirror the branches you are interested in, make a script that runs bzr pull in each, run the script manually or with cron
[00:08] <zsquareplusc> alternatively use a site that sends mail on changes, e.g. launchpad can do that
[00:09] <jelmer> I think it would make sense for bzr-notify to support polling
[00:11]  * zsquareplusc could use that too if it would support sftp:// :-)
[00:12]  * zsquareplusc has some private branches on a box with just 32MB RAM so he uses sftp because of the fear that a smart server would use to much resources
[00:17] <SamB_XP_> zsquareplusc: that's *so* 1997!
[00:19] <zsquareplusc> SamB_XP_: nah, it's a "modern" NSLU2, that uses less than 10W. i don't want to run old power hungry hardware 24/7...
[00:20] <SamB_XP_> zsquareplusc: is that some kind of PDA?
[00:22] <zsquareplusc> SamB_XP_: no, a small embedded box with 2xUSB+Ethernet. supported by Debian/Linux :-)
[00:22] <SamB_XP_> debian can still run on machines that tiny ?
[00:27] <zsquareplusc> yes. it has no display, so you don't have X and applets etc. that eat all the memory ;-)
[05:49] <jumpkick> how would one see the rev numbers associate with individual files in a workspace?
[05:49] <jumpkick> (normally I'd go on code.lp.net, but that's on the fritz)
[05:50] <bob2> as in, in which rev no a given file was last modified?
[05:51] <jumpkick> I think bzr log <file>
[05:51] <jumpkick> ?
[05:52] <jumpkick> that looks like it has the rev of the file at its last update
[05:53] <fullermd> That's probably the most straightforward way of getting it, yes.
[06:13] <jumpkick> thanks
[12:13] <bialix> fullermd: around?
[12:24] <timClicks> hi all, is there a way to automatically sync a branch with the shared repo?
[12:28] <bialix> branch and shared repo is the 2 different things
[13:04] <bac> good morning.  anyone here help maintain the bazaar-vcs.org site?  lots of broken links on the front page.
[13:06] <bac> abentley, jam1, spiv ^^
[13:07] <bialix> bac: it's a wiki
[13:07] <bialix> you can edit it
[13:09] <bac> bialix: ah, so it is.  had never noticed.
[13:09] <bialix> scroll down
[13:09] <bac> bialix: i see that now
[13:09] <bialix> k
[22:58] <DaffyDuck_> Let's say I do a "bzr checkout -r 10", and then fix a bug which was introduced there, how do I reset the working-tree later to "the latest revision" (such as it is now)?
[22:59] <DaffyDuck_> Ah. "bzr update"