Meta bug for cache in SeaMonkey

VERIFIED INVALID

Status

()

defect
P2
normal
VERIFIED INVALID
20 years ago
19 years ago

People

(Reporter: gagan, Assigned: warrensomebody)

Tracking

({meta})

Trunk
x86
Windows NT
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Depends on: 2860
Depends on: 2229
Depends on: 6869
Depends on: 7502
Depends on: 8500
Depends on: 9004
Depends on: 10062
Depends on: ClearAll
Depends on: 8305
Depends on: 2033
Depends on: 5252
Status: NEW → ASSIGNED
Target Milestone: M12
Priority: P3 → P2
Blocks: 5030
Moving Assignee from gagan to warren since he is away.
Assignee: warren → fur
Scott,

Can you look at the dependencies of this bug and mark them invalid if they are
invalid. I suspect that this is all (old) nu cache stuff.

Warren
No longer depends on: 5252
Depends on: 20838
Depends on: 20843
Depends on: 20851
Depends on: 20844
Depends on: 20845
No longer blocks: 5030
Depends on: 20893
Depends on: 21095
Depends on: 21100
Moving what's not done for M12 to M13.
Depends on: 21137
Depends on: 14772
Fuck, added an attachment to the wrong bug.
Depends on: 21162
Depends on: 21561
Depends on: 21569
Depends on: 21572
Depends on: 21578
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
Depends on: 21660
Assigning fur's cache bugs to Gordon. He can split them up with davidm.
Depends on: 23361
Assignee: gordon → warren
Target Milestone: M13 → M14
I'll take the meta bug.

(BTW, is fur@netscape.com still active?)
Keywords: meta
I'm not really using these meta-bugs any more for tracking, so I'm marking them 
REMIND to get them off the open list.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → REMIND
Sorry for the spam, changing QA contact.
QA Contact: paulmac → tever
reopening and marking INVALID since this is no longer being used...
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
inv
Status: REOPENED → RESOLVED
Closed: 20 years ago19 years ago
Resolution: --- → INVALID
vrfy invalid
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.