Closed
Bug 7232
Opened 26 years ago
Closed 25 years ago
[tracking] Old netlib bugs depending on new necko architechture
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: chofmann, Assigned: warrensomebody)
References
Details
Lots of bugs will be dependent on this one...
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M8
Assignee | ||
Comment 1•26 years ago
|
||
On target for M8.
Reporter | ||
Updated•26 years ago
|
Reporter | ||
Updated•26 years ago
|
Reporter | ||
Comment 2•26 years ago
|
||
reversing the dependency direction so these show up the dependency
tree for this bug
4863,5569,5675,5879,6188,6220,6293,6297,6324,7188,7229,7428,7450
Reporter | ||
Comment 3•26 years ago
|
||
adding 5665
Reporter | ||
Comment 4•26 years ago
|
||
adding 5665
Reporter | ||
Comment 5•26 years ago
|
||
adding ,2487,6017,6096,3248,4646,6090
Reporter | ||
Updated•26 years ago
|
Target Milestone: M8 → M9
Reporter | ||
Comment 7•26 years ago
|
||
necko now lands in m9
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.
Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change. If this happens, I will fix. ;-)
Reporter | ||
Updated•26 years ago
|
Summary: Necko Landing Tracking Bug → Old netlib bugs depending on new necko architechture
Reporter | ||
Updated•26 years ago
|
Target Milestone: M9 → M11
Assignee | ||
Updated•25 years ago
|
Summary: Old netlib bugs depending on new necko architechture → [tracking] Old netlib bugs depending on new necko architechture
Comment 10•25 years ago
|
||
ignore that dup.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•25 years ago
|
||
There's only one bug left in this list, so I'm closing this.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 12•25 years ago
|
||
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
You need to log in
before you can comment on or make changes to this bug.
Description
•