Ubuntu

bzr-gtk should not enable bzr-notify by default

Reported by to be removed on 2009-03-13
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Low
Unassigned
bzr-gtk (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: bzr-gtk

bzr-gtk version 0.95.0-1ubuntu6.

When I installed this package, to get "bzr viz", it installed a notification daemon into my session. This clutters up my notification area, and pops up a balloon when I commit. This does not seem to be useful in any scenario that I can think of: if I do a commit, I _know_ I did a commit. There is no point in notifying me about it.

bzr-gtk should not enable this by default. It is distracting and uses up computing resources without providing any benefit.

Related branches

lp:~jelmer/bzr-gtk/remove-bzr-notify
Merged into lp:bzr-gtk at revision 794
Vincent Ladeuil: Disapprove on 2012-07-09
Curtis Hovey: Approve (code) on 2012-07-09
Jelmer Vernooij (jelmer) wrote :

The main use case is notifying you of a "bzr pull" that you have running in the background that succeeded.

Jelmer Vernooij (jelmer) wrote :

fwiw, it also doesn't appear in the notification area by default in recent versions.

to be removed (liw) wrote :

Does it keep a process running in the background in recent versions?

If pulls that last a long time are the primary use case, it'd make sense to allow for that... but only if all other slow operations pop up nofications too. Such as removing a really large file under ext3 (can take minutes), doing ls when the NFS server is unavailable, or starting OpenOffice.

(In other words, I don't see why pulling is important enough to warrant notification, when all the other things are not. If I want notification, I'll ask for it, but I don't want it enabled all the time.)

Jelmer Vernooij (jelmer) on 2010-08-03
Changed in bzr-gtk (Ubuntu):
status: New → Confirmed
Changed in bzr-gtk:
status: New → Triaged
importance: Undecided → Low
Jesse Michael (jesse.michael) wrote :

This "feature" is especially aggravating when using the Netboot/Unity interface, as it takes up a significant amount of space in the left dock bar and is completely useless for my use cases.

I do a lot of bzr development, but I've never had any use for an additional status popup telling me what's going on in the terminal window I'm running my bzr commands from. I'm honestly having a little trouble figuring out when it would be useful.

On 16 December 2010 14:07, Jesse Michael <email address hidden> wrote:
> This "feature" is especially aggravating when using the Netboot/Unity
> interface, as it takes up a significant amount of space in the left dock
> bar and is completely useless for my use cases.
>
> I do a lot of bzr development, but I've never had any use for an
> additional status popup telling me what's going on in the terminal
> window I'm running my bzr commands from.  I'm honestly having a little
> trouble figuring out when it would be useful.

It's a start towards a project to tell you when other people are
committing to branches you're interested in. However, certainly the
only time I see notifications is about my own commits, or after I pull
commits into my own copy of a branch. In both cases, I already know
and I don't really need to be notified.

--
Martin

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers