1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
<html>
<head>
<title>What happens when I "mute" or "unmute" a bug?</title>
<link rel="stylesheet" type="text/css"
href="/+icing/yui/cssreset/reset.css" />
<link rel="stylesheet" type="text/css"
href="/+icing/yui/cssfonts/fonts.css" />
<link rel="stylesheet" type="text/css"
href="/+icing/yui/cssbase/base.css" />
</head>
<body>
<h1>What happens when I "mute" a bug?</h1>
<p>
Muting a bug tells Launchpad to stop sending you all email about
that bug.
</p>
<p>
This is most useful when you've subscribed to the bugs for an entire
milestone, series, project or distribution. If there's one bug that
doesn't interest you, you can mute it without affecting your overall
subscription.
</p>
<h2>Unmuting</h2>
<p>
When "unmuting" a bug you can choose what sorts of thing you want to
hear about, just like when you make a new subscription.
</p>
<h2>Muting bugs that come from a team subscription</h2>
<p>
If you are subscribed via a team, but the team delivers its bug mail
via a mailing list or some other team email address, you can't mute
bugs you hear about thanks to that subscription.
</p>
<p>
That's because in that case Launchpad delivers each email just once:
to the team's mailing list or other specified email address. So, it
can't filter out email intended specifically for you because it
doesn't exist.
</p>
<p>
Instead, you could try filtering the bug mail you receive via the
team's mailing list and then subscribing to the project's bugs
yourself. That will let you mute whichever bugs you like.
</p>
</body>
</html>
|