Fossil SCM
Mention the "worktree" git command in the Fossil-versus-Git document.
Commit
af91e0575e4293a931253fc7e8403e103950825113c34c35040e3d71765ec42c
Parent
3982569195e0518…
1 file changed
+10
-1
+10
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -180,19 +180,28 @@ | ||
| 180 | 180 | of the "unix philosophy". |
| 181 | 181 | |
| 182 | 182 | <h3>2.6 One vs. Many Check-outs per Repository</h3> |
| 183 | 183 | |
| 184 | 184 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 185 | -of a single check-out. The check-out and the repository are inseperable. | |
| 185 | +of a single check-out. The check-out and the repository are located | |
| 186 | +together in the filesystem. | |
| 186 | 187 | |
| 187 | 188 | With Fossil, a "repository" is a single SQLite database file |
| 188 | 189 | that can be stored anywhere. There |
| 189 | 190 | can be multiple active check-outs from the same repository, perhaps |
| 190 | 191 | open on different branches or on different snapshots of the same branch. |
| 191 | 192 | Long-running tests or builds can be running in one check-out while |
| 192 | 193 | changes are being committed in another. |
| 193 | 194 | |
| 195 | +(Update 2019-01-29:) | |
| 196 | +The check-out and the repository in Git used to be inseparable. | |
| 197 | +More recently, Git has been enhanced with the | |
| 198 | +"[https://git-scm.com/docs/git-worktree|worktree]" command that | |
| 199 | +allows a single repository to host multiple check-outs. However, | |
| 200 | +the interface is sufficiently difficult to use that most people | |
| 201 | +find it easier to create a separate clone for each check-out. | |
| 202 | + | |
| 194 | 203 | <h3>2.7 What you should have done vs. What you actually did</h3> |
| 195 | 204 | |
| 196 | 205 | Git puts a lot of emphasis on maintaining |
| 197 | 206 | a "clean" check-in history. Extraneous and experimental branches by |
| 198 | 207 | individual developers often never make it into the main repository. And |
| 199 | 208 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -180,19 +180,28 @@ | |
| 180 | of the "unix philosophy". |
| 181 | |
| 182 | <h3>2.6 One vs. Many Check-outs per Repository</h3> |
| 183 | |
| 184 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 185 | of a single check-out. The check-out and the repository are inseperable. |
| 186 | |
| 187 | With Fossil, a "repository" is a single SQLite database file |
| 188 | that can be stored anywhere. There |
| 189 | can be multiple active check-outs from the same repository, perhaps |
| 190 | open on different branches or on different snapshots of the same branch. |
| 191 | Long-running tests or builds can be running in one check-out while |
| 192 | changes are being committed in another. |
| 193 | |
| 194 | <h3>2.7 What you should have done vs. What you actually did</h3> |
| 195 | |
| 196 | Git puts a lot of emphasis on maintaining |
| 197 | a "clean" check-in history. Extraneous and experimental branches by |
| 198 | individual developers often never make it into the main repository. And |
| 199 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -180,19 +180,28 @@ | |
| 180 | of the "unix philosophy". |
| 181 | |
| 182 | <h3>2.6 One vs. Many Check-outs per Repository</h3> |
| 183 | |
| 184 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 185 | of a single check-out. The check-out and the repository are located |
| 186 | together in the filesystem. |
| 187 | |
| 188 | With Fossil, a "repository" is a single SQLite database file |
| 189 | that can be stored anywhere. There |
| 190 | can be multiple active check-outs from the same repository, perhaps |
| 191 | open on different branches or on different snapshots of the same branch. |
| 192 | Long-running tests or builds can be running in one check-out while |
| 193 | changes are being committed in another. |
| 194 | |
| 195 | (Update 2019-01-29:) |
| 196 | The check-out and the repository in Git used to be inseparable. |
| 197 | More recently, Git has been enhanced with the |
| 198 | "[https://git-scm.com/docs/git-worktree|worktree]" command that |
| 199 | allows a single repository to host multiple check-outs. However, |
| 200 | the interface is sufficiently difficult to use that most people |
| 201 | find it easier to create a separate clone for each check-out. |
| 202 | |
| 203 | <h3>2.7 What you should have done vs. What you actually did</h3> |
| 204 | |
| 205 | Git puts a lot of emphasis on maintaining |
| 206 | a "clean" check-in history. Extraneous and experimental branches by |
| 207 | individual developers often never make it into the main repository. And |
| 208 |