Closed Bug 13320 Opened 25 years ago Closed 25 years ago

[DOGFOOD] nsIFile not implemented

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Platform:
x86
All
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dougt, Assigned: dougt)

References

Details

(Whiteboard: [PDT-]) 

need to implmenent nsIFile
Status: NEW → ASSIGNED
Target Milestone: M13
looks like this has been punted on for beta.  I have been asked to do other
tasks.
Target Milestone: M13 → M14
not m13, but m14
Blocks: 11481
Target Milestone: M14 → M11
moving up to m11 per conversation with brendan.  Is this needed before beta?
QA Contact: beppe → gerardok
Summary: nsIFile not implemented → [DOGFOOD] nsIFile not implemented
brendan suggested that this be in before beta.  It is a major change to our
file object.  This will replace the nsFileSpec.
Whiteboard: [PDT-]
This s ok for Beta.  But not needed for dogfood. Putting on [PDT-] radar.
We need this well before beta to be "architecture complete".  I'm driving this
through porkjockeys.  FYI.

/be
Blocks: 9560, 11557, 12368, 15305
Blocks: 14468
Whiteboard: [PDT-] → [PDT?]
Target Milestone: M11 → M12
Adjusting milestone.  IS this PDT?
Blocks: 17432
This bug is a dependency of 14468, so it's porkjockey (PJ+, baby!) which trumps
PDT? any day.

/be
Whiteboard: [PDT?] → [PDT-]
This is porkjockey work, but not for dogfood, putting on PDT- radar.
Depends on: 17948
Depends on: 17949
Blocks: 18471
Blocks: 20203
Notice how no one ever votes for the important stuff?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I have checked in the windows implementation of nsIFile.  Marking as fixed.
No longer blocks: 9560
No longer blocks: 17432
No longer blocks: 18471
No longer blocks: 20203
You need to log in before you can comment on or make changes to this bug.