You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: UNIXFS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,8 +88,8 @@ UnixFS currently supports two optional metadata fields:
88
88
- The nine least significant bits represent `ugo-rwx`
89
89
- The next three least significant bits represent `setuid`, `setgid` and the `sticky bit`
90
90
- 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 maskoff bits without a defined meaning in the implemented version of the spec: `interpretedValue = originalValue & 07777`
93
93
*`mtime` -- The modification time in seconds since the epoch. This defaults to the unix epoch if unspecified
0 commit comments