Open
Bug 453975
Opened 16 years ago
Updated 2 years ago
[meta] Tracking bug to purge Mork from all Mozilla codebase
Categories
(MailNews Core :: Database, task, P3)
MailNews Core
Database
Tracking
(Not tracked)
NEW
People
(Reporter: davidaznarregue, Unassigned)
References
(Depends on 4 open bugs)
Details
(Keywords: meta)
User-Agent: Mozilla/5.0 (X11; rv:1.8.1.11) Gecko/20071128
Build Identifier:
Now that most Mozilla code is migrating to mozStorage is is time to purge the painful Mork from Mozilla codebase.
This a meta bug, so it should depend on any request to port from Mork to mozStorage.
It should probably block all Mork bugs since maybe work should be done in porting from Mork to mozStorage instead of trying to fix Mork bugs.
Reproducible: Always
Comment 1•16 years ago
|
||
isn't mork still used in Seamonkey and Thunderbird ?
Reporter | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> isn't mork still used in Seamonkey and Thunderbird ?
That is what this bug is for. To keep track of the modules that are still using Mork. Please make this bug depend on any bug to port any module from Mork, or if you know any module that still use Mork and there is no bug filled please file a bug and make this bug depend on it.
Updated•16 years ago
|
Updated•15 years ago
|
Component: General → Tracking
Keywords: meta
QA Contact: general → chofmann
Version: unspecified → Trunk
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Component: Tracking → Database
OS: Other → All
Product: Core → MailNews Core
QA Contact: chofmann → database
Hardware: Other → All
Updated•14 years ago
|
Component: Database → Tracking
Product: MailNews Core → Core
QA Contact: database → chofmann
Updated•8 years ago
|
Component: Tracking → Database
Product: Core → MailNews Core
QA Contact: chofmann
Updated•5 years ago
|
Type: defect → task
Priority: -- → P3
Comment 3•3 years ago
|
||
Can this one block this?
https://bugzilla.mozilla.org/show_bug.cgi?id=1669589
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•