Proposal change notifications come before initial proposal notification
Bug #356195 reported by
William Grant
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Tim Penhey | ||
Bug Description
If I create a merge proposal and then quickly set a commit message, I will be immediately notified of the commit message change. It will have no In-Reply-To.
A couple of minutes later I'll get a notification about the initial proposal - this latency might be because of the diff generation, which is fine. The problem is that this notification's In-Reply-To is the Message-ID of the commit message change notification. That's quite the wrong way around.
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: code-review email |
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in launchpad-code: | |
| assignee: | nobody → Tim Penhey (thumper) |
| status: | Triaged → Fix Released |
| Changed in launchpad: | |
| milestone: | none → 11.01 |
To post a comment you must log in.
This was fixed earlier this year.