"bzr commit-notify" should listen for Revision signals from any source

[James Henstridge]

I've been working on some improvements to bzr-dbus that change the way the "Revision" signals are emitted. With the changes there is no longer any broadcast daemon, and the signals originate from either from the process where the branch change occurred or from the lan-notify process (for network changes).

The attached branch updates the "bzr commit-notify" to watch for "Revision" signals from any source. This makes it work with both existing bzr-dbus and bzr-dbus with my changes.

[Daniel Schierbeck (dasch)]

This looks nice. I've also been thinking of adding auto-updating to the branch visualization tool, making it respond to commits, pulls, and merges. I think it would nice not having to restart it each time you make a change. I'll see if I can reuse some of your code to accomplish that.

[Jelmer Vernooij (jelmer)]

Hi James,

On Di, 2008-03-25 at 09:46 +0000, James Henstridge wrote:
> I've been working on some improvements to bzr-dbus that change the way
> the "Revision" signals are emitted. With the changes there is no longer
> any broadcast daemon, and the signals originate from either from the
> process where the branch change occurred or from the lan-notify process
> (for network changes).
>
> The attached branch updates the "bzr commit-notify" to watch for
> "Revision" signals from any source. This makes it work with both
> existing bzr-dbus and bzr-dbus with my changes.
Thanks! Getting rid of the broadcast daemon is a very useful change. Any
chance you could send a merge request for this to the bzr-gtk mailing
list? (<email address hidden>).

Cheers,

Jelmer

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

[James Henstridge (jamesh)]

I've sent a bundle to the list, which is currently sitting in the moderation queue.

[James Henstridge (jamesh)]

The fix has been merged to lp:bzr-gtk in r462.