Closed
Bug 129902
Opened 21 years ago
Closed 21 years ago
Sync up the NSPR client branch with the NSPR tip
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0
People
(Reporter: wtc, Assigned: wtc)
References
(Depends on 2 open bugs)
Details
Attachments
(1 file, 1 obsolete file)
87.80 KB,
patch
|
dbaron
:
approval+
|
Details | Diff | Splinter Review |
I would like to check in the latest NSPR bug fixes in the NSPRPUB_PRE_4_2_CLIENT_BRANCH. The NSPR 4.2 release is imminent. I'd like the mozilla 1.0 release to use NSPR 4.2 RTM. I will attach a patch and add the bug fixes as dependencies of this bug. The Mozilla client does not need any of these fixes; otherwise they would have been checked in the NSPRPUB_PRE_4_2_CLIENT_BRANCH. Some of these bug fixes are nice to have (such as fixing the one-time leaks of static objects) while others are just cosmetic changes (such as fixing the license headers and benign compiler warnings).
Assignee | ||
Comment 1•21 years ago
|
||
Assignee | ||
Comment 2•21 years ago
|
||
Here is a list of the changes in this patch that are of interest to the Mozilla client. HP-UX 11.20 port Memory leak fixes contributed by jeff@NerdOne.com bug 94153 bug 95659 bug 95668 bug 95773 bug 95784 bug 95817 bug 95836 bug 95839 bug 96112 bug 96122 bug 96197 bug 96198 bug 96199 NPL -> MPL/GPL bug 98741 Miscellaneous bug fixes bug 96571 bug 106496 bug 119935 bug 121872
Assignee | ||
Comment 3•21 years ago
|
||
Fixed a merging problem in the previous patch.
Attachment #73416 -
Attachment is obsolete: true
Comment 4•21 years ago
|
||
Comment on attachment 73435 [details] [diff] [review] Combined patch of all the bug fixes a=dbaron on behalf of drivers
Attachment #73435 -
Flags: review+
Updated•21 years ago
|
Attachment #73435 -
Flags: review+ → approval+
Assignee | ||
Comment 5•21 years ago
|
||
The deed is done. Marked the bug fixed.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•