Fossil SCM
Applied the new div class=sidebar styling to a few more cases in the docs.
Commit
701ea4d00410858cfde65519e2abbc4da410e7456494279edfd81faf2ae672a2
Parent
01764fea862df24…
2 files changed
+9
-9
+4
-6
+9
-9
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -79,10 +79,19 @@ | ||
| 79 | 79 | inline in messages, but each user may toggle that via the settings |
| 80 | 80 | popup menu, such that images instead appear as downloadable links. |
| 81 | 81 | Non-image files always appear in messages as download links. |
| 82 | 82 | |
| 83 | 83 | ### Deletion of Messages |
| 84 | + | |
| 85 | +<div class="sidebar">Message deletion is itself a type of message, which | |
| 86 | +is why deletions count towards updates in the recent activity list. (It | |
| 87 | +is counted for the person who performed the deletion, not the author of | |
| 88 | +the deleted comment.) That can potentially lead to odd corner cases | |
| 89 | +where a user shows up in the list but has no messages which are | |
| 90 | +currently visible because they were deleted, or an admin user who has | |
| 91 | +not posted anything but deleted a message. That is a known minor | |
| 92 | +cosmetic-only bug with a resolution of "will not fix."</div> | |
| 84 | 93 | |
| 85 | 94 | Any user may *locally* delete a given message by clicking on the "tab" |
| 86 | 95 | at the top of the message and clicking the button which appears. Such |
| 87 | 96 | deletions are local-only, and the messages will reappear if the page |
| 88 | 97 | is reloaded. The user who posted a given message, or any Admin users, |
| @@ -112,19 +121,10 @@ | ||
| 112 | 121 | show up in that list, nor does the chat infrastructure have a way to |
| 113 | 122 | track and present those. That list can be used to filter messages on a |
| 114 | 123 | specific user by tapping on that user's name, tapping a second time to |
| 115 | 124 | remove the filter. |
| 116 | 125 | |
| 117 | -Sidebar: message deletion is a type of message and deletions count | |
| 118 | -towards updates in the recent activity list (counted for the person | |
| 119 | -who performed the deletion, not the author of the deleted | |
| 120 | -comment). That can potentially lead to odd corner cases where a user | |
| 121 | -shows up in the list but has no messages which are currently visible | |
| 122 | -because they were deleted, or an admin user who has not posted | |
| 123 | -anything but deleted a message. That is a known minor cosmetic-only | |
| 124 | -bug with a resolution of "will not fix." | |
| 125 | - | |
| 126 | 126 | ### <a id="cli"></a> The `fossil chat` Command |
| 127 | 127 | |
| 128 | 128 | Type [fossil chat](/help?cmd=chat) from within any open check-out |
| 129 | 129 | to bring up a chatroom for the project that is in that checkout. |
| 130 | 130 | The new chat window will attempt to connect to the default sync |
| 131 | 131 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -79,10 +79,19 @@ | |
| 79 | inline in messages, but each user may toggle that via the settings |
| 80 | popup menu, such that images instead appear as downloadable links. |
| 81 | Non-image files always appear in messages as download links. |
| 82 | |
| 83 | ### Deletion of Messages |
| 84 | |
| 85 | Any user may *locally* delete a given message by clicking on the "tab" |
| 86 | at the top of the message and clicking the button which appears. Such |
| 87 | deletions are local-only, and the messages will reappear if the page |
| 88 | is reloaded. The user who posted a given message, or any Admin users, |
| @@ -112,19 +121,10 @@ | |
| 112 | show up in that list, nor does the chat infrastructure have a way to |
| 113 | track and present those. That list can be used to filter messages on a |
| 114 | specific user by tapping on that user's name, tapping a second time to |
| 115 | remove the filter. |
| 116 | |
| 117 | Sidebar: message deletion is a type of message and deletions count |
| 118 | towards updates in the recent activity list (counted for the person |
| 119 | who performed the deletion, not the author of the deleted |
| 120 | comment). That can potentially lead to odd corner cases where a user |
| 121 | shows up in the list but has no messages which are currently visible |
| 122 | because they were deleted, or an admin user who has not posted |
| 123 | anything but deleted a message. That is a known minor cosmetic-only |
| 124 | bug with a resolution of "will not fix." |
| 125 | |
| 126 | ### <a id="cli"></a> The `fossil chat` Command |
| 127 | |
| 128 | Type [fossil chat](/help?cmd=chat) from within any open check-out |
| 129 | to bring up a chatroom for the project that is in that checkout. |
| 130 | The new chat window will attempt to connect to the default sync |
| 131 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -79,10 +79,19 @@ | |
| 79 | inline in messages, but each user may toggle that via the settings |
| 80 | popup menu, such that images instead appear as downloadable links. |
| 81 | Non-image files always appear in messages as download links. |
| 82 | |
| 83 | ### Deletion of Messages |
| 84 | |
| 85 | <div class="sidebar">Message deletion is itself a type of message, which |
| 86 | is why deletions count towards updates in the recent activity list. (It |
| 87 | is counted for the person who performed the deletion, not the author of |
| 88 | the deleted comment.) That can potentially lead to odd corner cases |
| 89 | where a user shows up in the list but has no messages which are |
| 90 | currently visible because they were deleted, or an admin user who has |
| 91 | not posted anything but deleted a message. That is a known minor |
| 92 | cosmetic-only bug with a resolution of "will not fix."</div> |
| 93 | |
| 94 | Any user may *locally* delete a given message by clicking on the "tab" |
| 95 | at the top of the message and clicking the button which appears. Such |
| 96 | deletions are local-only, and the messages will reappear if the page |
| 97 | is reloaded. The user who posted a given message, or any Admin users, |
| @@ -112,19 +121,10 @@ | |
| 121 | show up in that list, nor does the chat infrastructure have a way to |
| 122 | track and present those. That list can be used to filter messages on a |
| 123 | specific user by tapping on that user's name, tapping a second time to |
| 124 | remove the filter. |
| 125 | |
| 126 | ### <a id="cli"></a> The `fossil chat` Command |
| 127 | |
| 128 | Type [fossil chat](/help?cmd=chat) from within any open check-out |
| 129 | to bring up a chatroom for the project that is in that checkout. |
| 130 | The new chat window will attempt to connect to the default sync |
| 131 |
+4
-6
| --- www/delta-manifests.md | ||
| +++ www/delta-manifests.md | ||
| @@ -1,6 +1,10 @@ | ||
| 1 | 1 | # Delta Manifests |
| 2 | + | |
| 3 | +<div class="sidebar">Do not confuse these with the core [Fossil delta | |
| 4 | +format](./delta_format.wiki). This document describes an optional | |
| 5 | +feature not enabled by default.</div> | |
| 2 | 6 | |
| 3 | 7 | This article describes "delta manifests," a special-case form of |
| 4 | 8 | checkin manifest which is intended to take up far less space than |
| 5 | 9 | a normal checkin manifest, in particular for repositories with |
| 6 | 10 | many files. We'll see, however, that the space savings, if indeed |
| @@ -9,16 +13,10 @@ | ||
| 9 | 13 | This article assumes that the reader is at least moderately familiar |
| 10 | 14 | with Fossil's [artifact file format](./fileformat.wiki), in particular |
| 11 | 15 | the structure of checkin manifests, and it won't make much sense to |
| 12 | 16 | readers unfamiliar with that topic. |
| 13 | 17 | |
| 14 | -Sidebar: delta manifests are not to be confused with the core [Fossil | |
| 15 | -delta format](./delta_format.wiki). The former is a special-case form | |
| 16 | -of delta which applies *only* to checkin manifests whereas the latter | |
| 17 | -is a general-purpose delta compression which can apply to any | |
| 18 | -Fossil-stored data (including delta manifests). | |
| 19 | - | |
| 20 | 18 | # Background and Motivation of Delta Manifests |
| 21 | 19 | |
| 22 | 20 | A checkin manifest includes a list of every file in that checkin. A |
| 23 | 21 | moderately-sized project can easily have a thousand files, and every |
| 24 | 22 | checkin manifest will include those thousand files. As of this writing |
| 25 | 23 |
| --- www/delta-manifests.md | |
| +++ www/delta-manifests.md | |
| @@ -1,6 +1,10 @@ | |
| 1 | # Delta Manifests |
| 2 | |
| 3 | This article describes "delta manifests," a special-case form of |
| 4 | checkin manifest which is intended to take up far less space than |
| 5 | a normal checkin manifest, in particular for repositories with |
| 6 | many files. We'll see, however, that the space savings, if indeed |
| @@ -9,16 +13,10 @@ | |
| 9 | This article assumes that the reader is at least moderately familiar |
| 10 | with Fossil's [artifact file format](./fileformat.wiki), in particular |
| 11 | the structure of checkin manifests, and it won't make much sense to |
| 12 | readers unfamiliar with that topic. |
| 13 | |
| 14 | Sidebar: delta manifests are not to be confused with the core [Fossil |
| 15 | delta format](./delta_format.wiki). The former is a special-case form |
| 16 | of delta which applies *only* to checkin manifests whereas the latter |
| 17 | is a general-purpose delta compression which can apply to any |
| 18 | Fossil-stored data (including delta manifests). |
| 19 | |
| 20 | # Background and Motivation of Delta Manifests |
| 21 | |
| 22 | A checkin manifest includes a list of every file in that checkin. A |
| 23 | moderately-sized project can easily have a thousand files, and every |
| 24 | checkin manifest will include those thousand files. As of this writing |
| 25 |
| --- www/delta-manifests.md | |
| +++ www/delta-manifests.md | |
| @@ -1,6 +1,10 @@ | |
| 1 | # Delta Manifests |
| 2 | |
| 3 | <div class="sidebar">Do not confuse these with the core [Fossil delta |
| 4 | format](./delta_format.wiki). This document describes an optional |
| 5 | feature not enabled by default.</div> |
| 6 | |
| 7 | This article describes "delta manifests," a special-case form of |
| 8 | checkin manifest which is intended to take up far less space than |
| 9 | a normal checkin manifest, in particular for repositories with |
| 10 | many files. We'll see, however, that the space savings, if indeed |
| @@ -9,16 +13,10 @@ | |
| 13 | This article assumes that the reader is at least moderately familiar |
| 14 | with Fossil's [artifact file format](./fileformat.wiki), in particular |
| 15 | the structure of checkin manifests, and it won't make much sense to |
| 16 | readers unfamiliar with that topic. |
| 17 | |
| 18 | # Background and Motivation of Delta Manifests |
| 19 | |
| 20 | A checkin manifest includes a list of every file in that checkin. A |
| 21 | moderately-sized project can easily have a thousand files, and every |
| 22 | checkin manifest will include those thousand files. As of this writing |
| 23 |