launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #03480
Re: Fwd: [Merge] lp:~mbp/launchpad/mbp-trivial into lp:launchpad/devel
I think I found the root cause for this:
<matsubara> bigjools, we were focusing on the subscribers list, but
the root cause is that ~launchpad is set as the default review team.
that's why MP emails keeps on going to launchpad-bugs@. My suggestion
is to change that to the launchpad reviewers team but I want to talk
to bac first as I don't know why ~launchpad rather than
~launchpad-reviewers is set as the default
I can't set the default review team myself, but I think Brad can, so
I'm waiting on him to confirm and make the change.
Cheers,
Diogo
On Thu, May 13, 2010 at 11:32 PM, Diogo Matsubara
<matsubara@xxxxxxxxxxxxx> wrote:
> On Thu, May 13, 2010 at 10:51 AM, Martin Pool <mbp@xxxxxxxxxxxxx> wrote:
>> On 13 May 2010 14:36, Diogo Matsubara <matsubara@xxxxxxxxxxxxx> wrote:
>>> On Thu, May 13, 2010 at 9:24 AM, Martin Pool <mbp@xxxxxxxxxxxxx> wrote:
>>>> Does anyone know why I get this rejection after proposing a merge?
>>>>
>>>
>>> I think the reason is that ~launchpad (contact e-mail:
>>> launchpad-bugs@xxxxxxxxxxxxxxxx) is subscribed to lp:launchpad/devel.
>>> When you merge proposal a branch targeted to lp:launchpad/devel,
>>> subscribers of that branch get a notification. Since you're not
>>> subscribed to the list, you get the reject email.
>>
>> OK, that is logical but also a kind of silly outcome. Do you want
>> merge proposal mail sent to that list?
>>
> Nope. I'm not sure if someone changed the settings afterwards but looking at:
> https://code.edge.launchpad.net/~launchpad-pqm/launchpad/devel/+subscription/launchpad
> all the options to not receive email are checked.
>
> Maybe we should unsubscribe ~launchpad from lp:launchpad/devel?
> ~launchpad-hackers is
> already subscribed to that branch.
>
> I think someone from the Code team can tell us better if my hypothesis is true.
>
> Cheers,
> --
> Diogo M. Matsubara
>
--
Diogo M. Matsubara
Follow ups
References