Fossil SCM
Linking to the new docs from fossil-v-git.wiki, simplifying it a bit.
Commit
ff428f3e091c9da98f39c5c34088b166de6f81cfe1e9e1b8fca9303338128d77
Parent
31f8a835dafbe8a…
1 file changed
+4
-5
+4
-5
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -645,21 +645,20 @@ | ||
| 645 | 645 | standard advice is to use a switch-in-place workflow in Fossil when |
| 646 | 646 | the disturbance from switching branches is small, and to use multiple |
| 647 | 647 | checkouts when you have long-lived working branches that are different |
| 648 | 648 | enough that switching in place is disruptive. |
| 649 | 649 | |
| 650 | -You can use Git in the Fossil style, either by manually symlinking the | |
| 651 | -<tt>.git</tt> directory from one working directory to another or by use | |
| 652 | -of the <tt>[https://git-scm.com/docs/git-worktree|git-worktree]</tt> | |
| 653 | -feature. Nevertheless, Git's default tie between working directory and | |
| 650 | +While you can [./gitusers.md#worktree | use Git in the Fossil style], | |
| 651 | +feature, Git's default tie between working directory and | |
| 654 | 652 | repository means the standard method for working with a Git repo is to |
| 655 | 653 | have one working directory only. Most Git tutorials teach this style, so |
| 656 | 654 | it is how most people learn to use Git. Because relatively few people |
| 657 | 655 | use Git with multiple working directories per repository, there are |
| 658 | 656 | [https://duckduckgo.com/?q=git+worktree+problem | several known |
| 659 | 657 | problems] with that way of working, problems which don't happen in Fossil because of |
| 660 | -the clear separation between repository and working directory. | |
| 658 | +the clear [./ckout-workflows.md | separation] between a Fossil repository and | |
| 659 | +each working directory. | |
| 661 | 660 | |
| 662 | 661 | This distinction matters because switching branches inside a single working directory loses local context |
| 663 | 662 | on each switch. |
| 664 | 663 | |
| 665 | 664 | For instance, in any software project where the runnable program must be |
| 666 | 665 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -645,21 +645,20 @@ | |
| 645 | standard advice is to use a switch-in-place workflow in Fossil when |
| 646 | the disturbance from switching branches is small, and to use multiple |
| 647 | checkouts when you have long-lived working branches that are different |
| 648 | enough that switching in place is disruptive. |
| 649 | |
| 650 | You can use Git in the Fossil style, either by manually symlinking the |
| 651 | <tt>.git</tt> directory from one working directory to another or by use |
| 652 | of the <tt>[https://git-scm.com/docs/git-worktree|git-worktree]</tt> |
| 653 | feature. Nevertheless, Git's default tie between working directory and |
| 654 | repository means the standard method for working with a Git repo is to |
| 655 | have one working directory only. Most Git tutorials teach this style, so |
| 656 | it is how most people learn to use Git. Because relatively few people |
| 657 | use Git with multiple working directories per repository, there are |
| 658 | [https://duckduckgo.com/?q=git+worktree+problem | several known |
| 659 | problems] with that way of working, problems which don't happen in Fossil because of |
| 660 | the clear separation between repository and working directory. |
| 661 | |
| 662 | This distinction matters because switching branches inside a single working directory loses local context |
| 663 | on each switch. |
| 664 | |
| 665 | For instance, in any software project where the runnable program must be |
| 666 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -645,21 +645,20 @@ | |
| 645 | standard advice is to use a switch-in-place workflow in Fossil when |
| 646 | the disturbance from switching branches is small, and to use multiple |
| 647 | checkouts when you have long-lived working branches that are different |
| 648 | enough that switching in place is disruptive. |
| 649 | |
| 650 | While you can [./gitusers.md#worktree | use Git in the Fossil style], |
| 651 | feature, Git's default tie between working directory and |
| 652 | repository means the standard method for working with a Git repo is to |
| 653 | have one working directory only. Most Git tutorials teach this style, so |
| 654 | it is how most people learn to use Git. Because relatively few people |
| 655 | use Git with multiple working directories per repository, there are |
| 656 | [https://duckduckgo.com/?q=git+worktree+problem | several known |
| 657 | problems] with that way of working, problems which don't happen in Fossil because of |
| 658 | the clear [./ckout-workflows.md | separation] between a Fossil repository and |
| 659 | each working directory. |
| 660 | |
| 661 | This distinction matters because switching branches inside a single working directory loses local context |
| 662 | on each switch. |
| 663 | |
| 664 | For instance, in any software project where the runnable program must be |
| 665 |