The [Branch foo] part in branch notification hides the important information in small email windows

[Björn Tillenius]

Each branch notification's subject start with something like:

  [Branch ~launchpad-pqm/launchpad/devel]

This is rather long. In fact for, Launchpad revision notifications, all I see in my default mail listing is:

  [Branch ~launchpad-pqm/launchpad/devel] Re

That tells me nothing about the notification, except which branch it is, which isn't important to me (I filter all the notification about that branch into a special folder.).

It would be nice if we could simply remove the [Branch foo] part. If we still want it, could we at least move it to the end?

[Jonathan Lange (jml)]

I remember mentioning this when the feature first landed :)

[Stuart Bishop (stub)]

Please don't do this until Bug 298284 is addressed or there is some alternative method of filtering the messages.

[Björn Tillenius (bjornt)]

On Mon, Nov 17, 2008 at 06:40:53AM -0000, Stuart Bishop wrote:
> Please don't do this until Bug 298284 is addressed or there is some
> alternative method of filtering the messages.

There is already the X-Launchpad-Branch header, which provides the same
information as the subject prefix.

Ah, I see now that the bug description talks about Gmail, and not
filtering in general... is filing a bug on Gmail a viable option, or
telling the users not to use Gmail if they want to be productive with
e-mail? ;)

[Max Bowsher (maxb)]

Please don't do this (without making it configurable, anyway), I care about receiving branch notification email to tell me when activity is going on in quieter projects (e.g. guice, irssi) and I don't have a separate folder and filtering rules for every branch I subscribe to. In fact, I read Launchpad branch notification emails directly in my inbox. Having the originating branch in the subject is an incredibly important piece of information in this use case.

[Robert Collins (lifeless)]

We could in principle allow per-subscription customisation of this, but I'd rather that we find a good compromise (e.g. put the branch on the right) and then stick with it.

I'm half inclined to wont-fix this, as its not particularly verbose today, and having a wider column in mail clients is pretty easy to do.