http://lxr.mozilla.org/seamonkey/search?string=nsMsgSortOrder shows the three enums defined by enum nsMsgSortOrder are all unused.
Ditto : http://lxr.mozilla.org/seamonkey/search?string=nsMsgSortType . Am I missing something? Since TBird is becoming the flagship, should I be looking there instead? (I happened upon these whil looking to change the default sort from ascending to descending.)
You should change both Seamonkey and TBird, if you have the time.
Matthew, are you planning on working on this? If not, can you/I punt it back to email@example.com?
Belatedly punting. My compile platform is out of commission, no time to fix.
Assignee: bugzillaPost120030in → nobody
Assignee: nobody → mail
Severity: normal → trivial
QA Contact: esther
Created attachment 285770 [details] [diff] [review] Remove nsMsgSortOrder and nsMsgSortType According to MXR neither nsMsgSortOrder nor nsMsgSortType are used anywhere in the code.
Summary: Code cleanup: nsMsgSortOrder → Code cleanup: nsMsgSortOrder and nsMsgSortType
Comment on attachment 285770 [details] [diff] [review] Remove nsMsgSortOrder and nsMsgSortType thx for the patch
Attachment #285770 - Flags: superreview?(bienvenu) → superreview+
Comment on attachment 285770 [details] [diff] [review] Remove nsMsgSortOrder and nsMsgSortType JFTR: we're using nsMsgViewSortOrder and nsMsgViewSortType these days. Landed on trunk.
Attachment #285770 - Flags: review?(mnyromyr) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
OS: Windows XP → All
Hardware: PC → All
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.