Skip to content

Commit ace8b9d

Browse files
Apply suggestions from code review
Incorporate suggestions from @achingbrain Co-Authored-By: Alex Potsides <[email protected]>
1 parent e5cff32 commit ace8b9d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

UNIXFS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,8 +88,8 @@ UnixFS currently supports two optional metadata fields:
8888
- The nine least significant bits represent `ugo-rwx`
8989
- The next three least significant bits represent `setuid`, `setgid` and the `sticky bit`
9090
- The remaining 20 bits are reserved for future use, and are subject to change. Spec implementations **MUST** handle bits they do not expect as follows:
91-
- For future-proofing the (de)serialization layer must preserve the entre uint32 value during clone/copy operations, modifying only bit values that have a well defined meaning: `clonedValue = ( modifiedBits & 07777 ) | ( originalValue & 0xFFFFF000 )`
92-
- Any higher level operations interpreting the value must proactively mask-off bits without a defined meaning in the current version of the spec: `interpretedValue = originalValue & 07777`
91+
- For future-proofing the (de)serialization layer must preserve the entire uint32 value during clone/copy operations, modifying only bit values that have a well defined meaning: `clonedValue = ( modifiedBits & 07777 ) | ( originalValue & 0xFFFFF000 )`
92+
- Implementations of this spec must proactively mask off bits without a defined meaning in the implemented version of the spec: `interpretedValue = originalValue & 07777`
9393
* `mtime` -- The modification time in seconds since the epoch. This defaults to the unix epoch if unspecified
9494

9595
### Deduplication and inlining

0 commit comments

Comments
 (0)