Closed Bug 1212510 Opened 10 years ago Closed 10 years ago

Bustage fix: Rename NS_ParseContentType to NS_ParseResponseContentType (caused by Bug 1210302)

Categories

(MailNews Core :: Backend, defect)

defect
Not set
blocker

Tracking

(thunderbird42 fixed, thunderbird43 fixed, thunderbird44 fixed, thunderbird_esr38 unaffected)

RESOLVED FIXED
Thunderbird 44.0
Tracking Status
thunderbird42 --- fixed
thunderbird43 --- fixed
thunderbird44 --- fixed
thunderbird_esr38 --- unaffected

People

(Reporter: philip.chee, Assigned: philip.chee)

References

()

Details

(Keywords: dogfood)

Attachments

(1 file)

No description provided.
> You are not authorized to access bug 1210302. :P
Assignee: nobody → philip.chee
Attachment #8670952 - Flags: review?(ehsan)
Attachment #8670952 - Flags: review?(Pidgeot18)
Comment on attachment 8670952 [details] [diff] [review] Patch s/NS_ParseContentType/NS_ParseResponseContentType/ I don't know this code, sorry.
Attachment #8670952 - Flags: review?(ehsan)
Comment on attachment 8670952 [details] [diff] [review] Patch s/NS_ParseContentType/NS_ParseResponseContentType/ Review of attachment 8670952 [details] [diff] [review]: ----------------------------------------------------------------- Without revealing the purpose of the changes in bug 1210302, I will say that this patch is safe because the implementations here are implementations of nsIChannel::SetContentType, and the changed code would be equivalent to nsBaseChannel::SetContentType. Bug 1210302 does raise other questions, but I think there are no changes needed to Thunderbird code as a result.
Attachment #8670952 - Flags: review?(Pidgeot18) → review+
Comment on attachment 8670952 [details] [diff] [review] Patch s/NS_ParseContentType/NS_ParseResponseContentType/ https://hg.mozilla.org/comm-central/rev/5d74f3155ba2
Thanks for the fix! Pushing now since this is a blocker.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 44.0
Severity: normal → blocker
Keywords: dogfood
http://hg.mozilla.org/releases/mozilla-aurora/rev/adae4392080b was pushed, so we're busted in c-a as well.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment on attachment 8670952 [details] [diff] [review] Patch s/NS_ParseContentType/NS_ParseResponseContentType/ [Approval Request Comment] Regression caused by (bug #): 1210302 User impact if declined: cannot build Testing completed (on c-c, etc.): Risk to taking this patch (and alternatives if risky):
Attachment #8670952 - Flags: approval-comm-aurora?
Comment on attachment 8670952 [details] [diff] [review] Patch s/NS_ParseContentType/NS_ParseResponseContentType/ [Approval Request Comment] Regression caused by (bug #): User impact if declined: Testing completed (on c-c, etc.): Risk to taking this patch (and alternatives if risky):
Attachment #8670952 - Flags: approval-comm-beta?
(In reply to Edmund Wong (:ewong) from comment #8) > Comment on attachment 8670952 [details] [diff] [review] > Patch s/NS_ParseContentType/NS_ParseResponseContentType/ > > [Approval Request Comment] > Regression caused by (bug #): > User impact if declined: > Testing completed (on c-c, etc.): > Risk to taking this patch (and alternatives if risky): It was also pushed to m-b.
Status tracks the trunk status. Use flags for branch tracking.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Attachment #8670952 - Flags: approval-comm-beta?
Attachment #8670952 - Flags: approval-comm-beta+
Attachment #8670952 - Flags: approval-comm-aurora?
Attachment #8670952 - Flags: approval-comm-aurora+
The patch forcing these changes will be pushed to mozilla-esr38, but the current plans are to do that in an esr-safe manner that does not require this patch.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: