Closed
Bug 476230
Opened 17 years ago
Closed 17 years ago
remove all MoreFilesX usage
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.9.2a1
People
(Reporter: jaas, Assigned: jaas)
References
Details
Attachments
(1 file)
|
256.93 KB,
patch
|
smichaud
:
review+
dougt
:
superreview+
|
Details | Diff | Splinter Review |
This bug is specifically about removing all MoreFilesX usage from the tree and removing the MoreFilesX component. This is part of bug 456662.
Attachment #359848 -
Flags: review?(smichaud)
Updated•17 years ago
|
Attachment #359848 -
Flags: review?(smichaud) → review+
Comment 2•17 years ago
|
||
Comment on attachment 359848 [details] [diff] [review]
fix v1.0
Aside from one minor mistake, this looks fine to me.
In nsLocalFile::GetFileCreator(), this:
+ id creatorNum = (NSNumber*)[dict objectForKey:NSFileHFSCreatorCode];
should really be this:
+ NSNumber* creatorNum = (NSNumber*)[dict objectForKey:NSFileHFSCreatorCode];
I also have one observation. It's not an objection -- I just want to
note it for future reference. (And I somehow missed it when reviewing
this patch's predecessor at bug 456662.)
nsLocalFile::InitWithFSSpec() and nsLocalFile::GetFSSpec()
(apparently) originally fell back to using the parent directory (or
trying to use it) on an error. I'm not sure this ever made much sense
... but in any case you've gotten rid of it.
I compiled and tested this patch ... but I'm not entirely sure how it
should be tested. I just ran the browser and opened a local file.
Everything worked fine.
Attachment #359848 -
Flags: superreview?(doug.turner)
Updated•17 years ago
|
Attachment #359848 -
Flags: superreview?(doug.turner) → superreview+
pushed to mozilla-central, forgot to make the change Steven suggested, will follow up
http://hg.mozilla.org/mozilla-central/rev/85e381233997
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Target Milestone: --- → mozilla1.9.2a1
Comment 4•17 years ago
|
||
This should probably be backed out right away -- it appears to have caused bug 478549.
You need to log in
before you can comment on or make changes to this bug.
Description
•