responses to (bugs, merge proposals) via email are permitted any subject and then passed on to subscribers

Bug #419252 reported by John A Meinel on 2009-08-26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

I don't know how this is specifically happening, but I'm seeing merge proposal threads that have *very* different mail headers.

For example the thread from here:

My first email is:
[Merge] lp:~lifeless/bzr/test-speed into lp:bzr

for which I see a reply from John Arbash Meinel (myself) of:
Re: [Merge] lp:~lifeless/bzr/test-speed into lp:bzr

But then a while later I see a response from Vincent Ladeuil:
Re: Various test_selftest improvements

My guess is that somehow Vincent is getting a copy of the merge proposal which is very different from the copy I'm getting. Potentially Robert submitted the request via email and Vincent got a copy of it but I didn't?

I'm pretty sure that I'm not subscribed directly to the 'bzr' branch, and Vincent might be. So it may be that I'm in "bzr-core" and Vincent is directly subscribed, so we are seeing different emails.

The most annoying part is that it breaks threading. So in my folder with all the code reviews, it is completely unclear what review Vincent is replying to.

Another possibility: Reply via email versus reply versus web interface

Vincent Ladeuil (vila) wrote :

I used the web interface to reply.

More precisely I clicked the Reply button on Robert's comment.
I see the same headers than John, highly misleading (and we were both involved...).

Changed in launchpad-code:
status: New → Confirmed
John A Meinel (jameinel) wrote :

So it looks like it might be the case if you reply to a specific comment, rather than replying to the overall merge proposal.

At least, that is something to look at.

Aaron Bentley (abentley) on 2010-01-07
tags: added: email
Curtis Hovey (sinzui) on 2010-12-24
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → Low
summary: - merge proposal threads have different headers
+ responses to (bugs, merge proposals) via email are permitted any subject
+ and then passed on to subscribers
tags: added: bugs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers