Fossil SCM
Documented the 'l' F-card permission and added a minor clarification regarding F-card UUID values for removed files.
Commit
007c32bdfd677111a55f4a54299f5014d4a27f90
Parent
3fbdaa243d1832c…
1 file changed
+21
-21
+21
-21
| --- www/fileformat.wiki | ||
| +++ www/fileformat.wiki | ||
| @@ -138,31 +138,31 @@ | ||
| 138 | 138 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><br> |
| 139 | 139 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><b>.</b><i>SSS</i> |
| 140 | 140 | </blockquote> |
| 141 | 141 | |
| 142 | 142 | A manifest has zero or more F-cards. Each F-card identifies a file |
| 143 | -that is part of the check-in. There are one, two, three, or four arguments. | |
| 144 | -The first argument | |
| 145 | -is the pathname of the file in the check-in relative to the root | |
| 146 | -of the project file hierarchy. No ".." or "." directories are allowed | |
| 147 | -within the filename. Space characters are escaped as in C-card | |
| 148 | -comment text. Backslash characters and newlines are not allowed | |
| 149 | -within filenames. The directory separator character is a forward | |
| 150 | -slash (ASCII 0x2F). The second argument to the F-card is the | |
| 151 | -full 40-character lower-case hexadecimal SHA1 hash of the content | |
| 152 | -artifact. The second argument is required for baseline manifests | |
| 153 | -but is optional for delta manifests. When the second argument to the | |
| 154 | -F-card is omitted, it means that the file has been deleted relative | |
| 155 | -to the baseline. The optional 3rd argument defines any special access | |
| 156 | -permissions associated with the file. The only special code currently | |
| 157 | -defined is "x" which means that the file is executable. All files are | |
| 158 | -always readable and writable. This can be expressed by "w" permission | |
| 159 | -if desired but is optional. The file format might be extended with | |
| 160 | -new permission letters in the future. | |
| 161 | -The optional 4th argument is the name of the same file as it existed in | |
| 162 | -the parent check-in. If the name of the file is unchanged from its | |
| 163 | -parent, then the 4th argument is omitted. | |
| 143 | +that is part of the check-in. There are one, two, three, or four | |
| 144 | +arguments. The first argument is the pathname of the file in the | |
| 145 | +check-in relative to the root of the project file hierarchy. No ".." | |
| 146 | +or "." directories are allowed within the filename. Space characters | |
| 147 | +are escaped as in C-card comment text. Backslash characters and | |
| 148 | +newlines are not allowed within filenames. The directory separator | |
| 149 | +character is a forward slash (ASCII 0x2F). The second argument to the | |
| 150 | +F-card is the full 40-character lower-case hexadecimal SHA1 hash of | |
| 151 | +the content artifact. The second argument is required for baseline | |
| 152 | +manifests but is optional for delta manifests. When the second | |
| 153 | +argument to the F-card is omitted, it means that the file has been | |
| 154 | +deleted relative to the baseline (files removed in baseline manifests | |
| 155 | +versions are <em>not</em> added as F-cards). The optional 3rd argument | |
| 156 | +defines any special access permissions associated with the file. This | |
| 157 | +can be defined as "x" to mean that the file is executable or "l" | |
| 158 | +(small letter ell) to mean a symlink. All files are always readable | |
| 159 | +and writable. This can be expressed by "w" permission if desired but | |
| 160 | +is optional. The file format might be extended with new permission | |
| 161 | +letters in the future. The optional 4th argument is the name of the | |
| 162 | +same file as it existed in the parent check-in. If the name of the | |
| 163 | +file is unchanged from its parent, then the 4th argument is omitted. | |
| 164 | 164 | |
| 165 | 165 | A manifest has zero or one N-cards. The N-card specifies the mimetype for the |
| 166 | 166 | text in the comment of the C-card. If the N-card is omitted, a default mimetype |
| 167 | 167 | is used. |
| 168 | 168 | |
| 169 | 169 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -138,31 +138,31 @@ | |
| 138 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><br> |
| 139 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><b>.</b><i>SSS</i> |
| 140 | </blockquote> |
| 141 | |
| 142 | A manifest has zero or more F-cards. Each F-card identifies a file |
| 143 | that is part of the check-in. There are one, two, three, or four arguments. |
| 144 | The first argument |
| 145 | is the pathname of the file in the check-in relative to the root |
| 146 | of the project file hierarchy. No ".." or "." directories are allowed |
| 147 | within the filename. Space characters are escaped as in C-card |
| 148 | comment text. Backslash characters and newlines are not allowed |
| 149 | within filenames. The directory separator character is a forward |
| 150 | slash (ASCII 0x2F). The second argument to the F-card is the |
| 151 | full 40-character lower-case hexadecimal SHA1 hash of the content |
| 152 | artifact. The second argument is required for baseline manifests |
| 153 | but is optional for delta manifests. When the second argument to the |
| 154 | F-card is omitted, it means that the file has been deleted relative |
| 155 | to the baseline. The optional 3rd argument defines any special access |
| 156 | permissions associated with the file. The only special code currently |
| 157 | defined is "x" which means that the file is executable. All files are |
| 158 | always readable and writable. This can be expressed by "w" permission |
| 159 | if desired but is optional. The file format might be extended with |
| 160 | new permission letters in the future. |
| 161 | The optional 4th argument is the name of the same file as it existed in |
| 162 | the parent check-in. If the name of the file is unchanged from its |
| 163 | parent, then the 4th argument is omitted. |
| 164 | |
| 165 | A manifest has zero or one N-cards. The N-card specifies the mimetype for the |
| 166 | text in the comment of the C-card. If the N-card is omitted, a default mimetype |
| 167 | is used. |
| 168 | |
| 169 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -138,31 +138,31 @@ | |
| 138 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><br> |
| 139 | <i>YYYY</i><b>-</b><i>MM</i><b>-</b><i>DD</i><b>T</b><i>HH</i><b>:</b><i>MM</i><b>:</b><i>SS</i><b>.</b><i>SSS</i> |
| 140 | </blockquote> |
| 141 | |
| 142 | A manifest has zero or more F-cards. Each F-card identifies a file |
| 143 | that is part of the check-in. There are one, two, three, or four |
| 144 | arguments. The first argument is the pathname of the file in the |
| 145 | check-in relative to the root of the project file hierarchy. No ".." |
| 146 | or "." directories are allowed within the filename. Space characters |
| 147 | are escaped as in C-card comment text. Backslash characters and |
| 148 | newlines are not allowed within filenames. The directory separator |
| 149 | character is a forward slash (ASCII 0x2F). The second argument to the |
| 150 | F-card is the full 40-character lower-case hexadecimal SHA1 hash of |
| 151 | the content artifact. The second argument is required for baseline |
| 152 | manifests but is optional for delta manifests. When the second |
| 153 | argument to the F-card is omitted, it means that the file has been |
| 154 | deleted relative to the baseline (files removed in baseline manifests |
| 155 | versions are <em>not</em> added as F-cards). The optional 3rd argument |
| 156 | defines any special access permissions associated with the file. This |
| 157 | can be defined as "x" to mean that the file is executable or "l" |
| 158 | (small letter ell) to mean a symlink. All files are always readable |
| 159 | and writable. This can be expressed by "w" permission if desired but |
| 160 | is optional. The file format might be extended with new permission |
| 161 | letters in the future. The optional 4th argument is the name of the |
| 162 | same file as it existed in the parent check-in. If the name of the |
| 163 | file is unchanged from its parent, then the 4th argument is omitted. |
| 164 | |
| 165 | A manifest has zero or one N-cards. The N-card specifies the mimetype for the |
| 166 | text in the comment of the C-card. If the N-card is omitted, a default mimetype |
| 167 | is used. |
| 168 | |
| 169 |