Cover letter for emailed merge proposal silently discarded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Aaron Bentley |
Bug Description
I submitted <https:/
As you can see from the original email, there's a lengthy "cover letter" in that email explaining the patch. Yet there is no sign of that text on the web page for that proposal, or in the email I received from Launchpad informing me that merge proposal was created.
I expected the text of the original email to be visible on the merge proposal, perhaps as the first "comment".
I certainly don't want filing merge proposals to be a multi-step process involving a web form; I regularly create them while off-line. As best I can tell the current process is "send request; wait a minute or five for email to reach LP and be processed; find web page for new merge proposal somehow; open that page; add cover letter to that page; submit". I want the process to be simply "run 'bzr send'", as it is for Bundle Buggy.
Changed in launchpad-code: | |
assignee: | nobody → Aaron Bentley (abentley) |
importance: | Undecided → High |
milestone: | none → 2.2.6 |
status: | New → In Progress |
tags: | added: code-review email |
Changed in launchpad-code: | |
milestone: | 2.2.6 → 2.2.7 |
milestone: | 2.2.7 → 2.2.6 |
status: | In Progress → Fix Released |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Bennetts wrote:
> As you can see from the original email, there's a lengthy "cover letter"
> in that email explaining the patch. Yet there is no sign of that text
> on the web page for that proposal, or in the email I received from
> Launchpad informing me that merge proposal was created.
That is indeed a bug. It doesn't happen to everyone, so it's been
unclear what the root cause is. Thanks for attaching the raw mail.
That will help.
> I expected the text of the original email to be visible on the merge
> proposal, perhaps as the first "comment".
That's what usually happens.
> As best I
> can tell the current process is "send request; wait a minute or five for
> email to reach LP and be processed; find web page for new merge proposal
> somehow;
That's a little worrying. When you create a merge proposal, you should
receive email about it, and that should include the URL.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAko 3maMACgkQ0F+ nu1YWqI1D6wCfT/ Ymgea05gMmNZPp8 SODKQq0 crUEcS0/ pKwIubRjU
+h0An06dQJ3IGcX
=oYV/
-----END PGP SIGNATURE-----