|
|
|
Andreas Savva: 06/20/2007 10:50 AM EDT
|
| |
Comment: |
Confirmed in draft 9
|
| |
Action: |
Update
Closed set to 06/20/2007
Status changed from Fixed to Closed
|
|
|
Andreas Savva: 06/13/2007 10:23 AM EDT
|
| |
Comment: |
Updated in draft 8 to include non-portable and use discouraged.
|
| |
Action: |
Update
|
|
|
Donal Fellows: 06/11/2007 11:16 AM EDT
|
| |
Comment: |
To me, ROOT should be described as non-portable and its use should be discouraged. But if people want to write things that refer to the root directory
, the ROOT FileSystemName is how to do it. (They're allowed to shoot themselves in the foot; we just describe the size of the ammo...)
|
| |
Action: |
Update
|
|
|
Andreas Savva: 04/11/2007 5:12 AM EDT
|
| |
Comment: |
- Changed "example definitions" to "normative definitions"
- Because of the above change I reformatted the section, moving the text from the Description element to be part of the definition of each filesystem
name.
Added security considerations for ROOT.
Should a deprecation note for ROOT also be added?
|
| |
Action: |
Update
Status changed from Resolved to Fixed
|
|
|
Donal Fellows: 04/05/2007 10:22 AM EDT
|
| |
Comment: |
IIRC, decision was that Root should be / on POSIX systems, but many systems might not provide it. I suppose it is more of a "It MUST mean this, but
MAY be absent."
|
| |
Action: |
Update
|
|
|
Andreas Savva: 04/04/2007 11:14 AM EDT
|
| |
Comment: |
Add cautionary note to not rely on having ROOT well-known.
|
| |
Action: |
Update
Status changed from Pending to Resolved
|
|
|
Andreas Savva: 01/17/2007 10:18 AM EST
|
| |
Comment: |
Consider ROOT usage; provide use case or remove
otherwise resolved as
- Make the type of filesystem normative.
- Specify other characteristics (typically shared or not) as informative.
|
| |
Action: |
Update
Assigned To set to Donal Fellows
Status changed from Open to Pending
|
|
|
|
