Closed
Bug 717402
Opened 12 years ago
Closed 12 years ago
Permanent orange: TEST-UNEXPECTED-FAIL | test-about-support.js | test-about-support.js::*
Categories
(Thunderbird :: Testing Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 12.0
People
(Reporter: mconley, Assigned: aceman)
References
Details
(Whiteboard: [fixed by bug 631909])
Attachments
(1 obsolete file)
The patch for bug 631909 changed the string key "aboutSupport.modifiedPrefsTitle" on us, and broke our about:support.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → mconley
Reporter | ||
Comment 1•12 years ago
|
||
Tests are now passing locally.
Reporter | ||
Comment 2•12 years ago
|
||
Comment on attachment 587811 [details] [diff] [review] Patch v1 This fixes it.
Attachment #587811 -
Flags: review?(mbanner)
No wonder. I specified in bug 631909 that both patches (for FF and TB) must be merged simultaneously. Dao only took the FF patch. Can you merge the other one? This bug should vanish.
Reporter | ||
Comment 5•12 years ago
|
||
Ah, k - I'll check in the patch in bug 631909.
Reporter | ||
Comment 6•12 years ago
|
||
Comment on attachment 587811 [details] [diff] [review] Patch v1 There's a patch in bug 631909 that fixes this - it just didn't get checked in to comm-central.
Attachment #587811 -
Attachment is obsolete: true
Attachment #587811 -
Flags: review?(mbanner)
Reporter | ||
Comment 7•12 years ago
|
||
The patch in bug 631909 (https://bugzilla.mozilla.org/attachment.cgi?id=583580) was committed to comm-central as http://hg.mozilla.org/comm-central/rev/c01205ffb4f8
Assignee: mconley → acelists
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 12.0
Can you tell me how to avoid this next time? I have several more bugs where there are patches for FF and TB that must be merged at once. But they must be done as two files due to 'hg mq' and possibly checkin rights of various people.
Hardware: x86_64 → All
Whiteboard: [fixed by bug 631909]
Reporter | ||
Comment 9•12 years ago
|
||
aceman: For things like this, I think it's enough to make sure that there's a TB developer CC'd on the bug. Pinging us in IRC also helps. :) -Mike
You need to log in
before you can comment on or make changes to this bug.
Description
•