Fossil SCM
Change to www/caps/index.md
Commit
0af46e5dc8c2de171c89eeeacbbba29addba31915b3803a5a1a28280277adbcf
Parent
d1d2298090f1fb6…
1 file changed
+1
-1
+1
-1
| --- www/caps/index.md | ||
| +++ www/caps/index.md | ||
| @@ -294,11 +294,11 @@ | ||
| 294 | 294 | Fossil requires write access to a repo DB while cloning from it, so you |
| 295 | 295 | can’t clone from a read-only repo DB file over a local file path. |
| 296 | 296 | |
| 297 | 297 | Even more surprising to you may be the fact that user caps do not affect |
| 298 | 298 | cloning and syncing over SSH! (Not unless you go [out of your way][sshfc] |
| 299 | -patch around it, at any rate.) When you make a change to such a | |
| 299 | +to patch around it, at any rate.) When you make a change to such a | |
| 300 | 300 | repository, the stock Fossil behavior is that the change first goes to the |
| 301 | 301 | local repo clone where file system |
| 302 | 302 | permissions are all that matter, but then upon sync, the situation is |
| 303 | 303 | effectively the same as when the parent repo is on the local file |
| 304 | 304 | system. The reason behind this is that if you can log into the remote |
| 305 | 305 |
| --- www/caps/index.md | |
| +++ www/caps/index.md | |
| @@ -294,11 +294,11 @@ | |
| 294 | Fossil requires write access to a repo DB while cloning from it, so you |
| 295 | can’t clone from a read-only repo DB file over a local file path. |
| 296 | |
| 297 | Even more surprising to you may be the fact that user caps do not affect |
| 298 | cloning and syncing over SSH! (Not unless you go [out of your way][sshfc] |
| 299 | patch around it, at any rate.) When you make a change to such a |
| 300 | repository, the stock Fossil behavior is that the change first goes to the |
| 301 | local repo clone where file system |
| 302 | permissions are all that matter, but then upon sync, the situation is |
| 303 | effectively the same as when the parent repo is on the local file |
| 304 | system. The reason behind this is that if you can log into the remote |
| 305 |
| --- www/caps/index.md | |
| +++ www/caps/index.md | |
| @@ -294,11 +294,11 @@ | |
| 294 | Fossil requires write access to a repo DB while cloning from it, so you |
| 295 | can’t clone from a read-only repo DB file over a local file path. |
| 296 | |
| 297 | Even more surprising to you may be the fact that user caps do not affect |
| 298 | cloning and syncing over SSH! (Not unless you go [out of your way][sshfc] |
| 299 | to patch around it, at any rate.) When you make a change to such a |
| 300 | repository, the stock Fossil behavior is that the change first goes to the |
| 301 | local repo clone where file system |
| 302 | permissions are all that matter, but then upon sync, the situation is |
| 303 | effectively the same as when the parent repo is on the local file |
| 304 | system. The reason behind this is that if you can log into the remote |
| 305 |