Fossil SCM
Minor tweaks to the gitusers doc to track the prior commit.
Commit
aa29ce14fd9a3c29c7f95d04ad969412e1d25eba14d9c8012952c8a39ebbe96e
Parent
b6b1b705d001178…
1 file changed
+13
-11
+13
-11
| --- www/gitusers.md | ||
| +++ www/gitusers.md | ||
| @@ -114,23 +114,23 @@ | ||
| 114 | 114 | [cw]: ./ckout-workflows.md |
| 115 | 115 | |
| 116 | 116 | |
| 117 | 117 | #### <a id="close" name="dotfile"></a> Closing A Check-Out |
| 118 | 118 | |
| 119 | -The `fossil close` command dissaociates a check-out directory from the | |
| 120 | -Fossil repository database, nondestructively inverting `fossil open`. It | |
| 119 | +The [`fossil close`][close] command dissaociates a check-out directory from the | |
| 120 | +Fossil repository database, nondestructively inverting [`fossil open`][open]. It | |
| 121 | 121 | won’t remove the managed files, and unless you give the `--force` |
| 122 | 122 | option, it won’t let you close the check-out with uncommitted changes to |
| 123 | 123 | those managed files. |
| 124 | 124 | |
| 125 | -The `close` command also refuses to run without `--force` when you have | |
| 125 | +The `close` command refuses to run without `--force` when you have | |
| 126 | 126 | certain precious per-checkout data, which Fossil stores in the |
| 127 | 127 | `.fslckout` file at the root of a check-out directory. This is a SQLite |
| 128 | 128 | database that keeps track of local state such as what version you have |
| 129 | 129 | checked out, the contents of the [stash] for that working directory, the |
| 130 | 130 | [undo] buffers, per-checkout [settings][set], and so forth. The stash |
| 131 | -and undo buffers are considered precious, being “uncommitted changes,” | |
| 131 | +and undo buffers are considered precious uncommitted changes, | |
| 132 | 132 | so you have to force Fossil to discard these as part of closing the |
| 133 | 133 | check-out. |
| 134 | 134 | |
| 135 | 135 | Thus, `.fslckout` is not the same thing as `.git`! |
| 136 | 136 | |
| @@ -137,23 +137,25 @@ | ||
| 137 | 137 | In native Windows builds of Fossil — that is, excluding Cygwin and WSL |
| 138 | 138 | builds, which follow POSIX conventions — this file is called `_FOSSIL_` |
| 139 | 139 | instead to get around the historical 3-character extension limit with |
| 140 | 140 | certain legacy filesystems. |
| 141 | 141 | |
| 142 | -Closing a check-out directory is a rare operation. One common use case | |
| 143 | -is that you’re about to delete it, so you want Fossil to forget about it | |
| 144 | -for the purposes of commands like [`fossil all`][all]. | |
| 142 | +Closing a check-out directory is a rare operation. One use case | |
| 143 | +is that you’re about to delete the directory, so you want Fossil to forget about it | |
| 144 | +for the purposes of commands like [`fossil all`][all]. Even that isn’t | |
| 145 | +necessary, because Fossil will detect that this has happened and forget | |
| 146 | +the working directory for you. | |
| 145 | 147 | |
| 146 | -The closest equivalent for `fossil close` in Git is | |
| 147 | -`git worktree remove`. | |
| 148 | +The closest equivalent in Git is `git worktree remove`. | |
| 148 | 149 | |
| 149 | 150 | [all]: /help?cmd=all |
| 150 | 151 | |
| 151 | 152 | |
| 152 | 153 | #### <a id="iip"></a> Init In Place |
| 153 | 154 | |
| 154 | -To illustrate these differences, consider this common Git “init in place” | |
| 155 | +To illustrate the differences that Fossil’s separation of repository | |
| 156 | +from working directory creates in practice, consider this common Git “init in place” | |
| 155 | 157 | method for creating a new repository from an existing tree of files, |
| 156 | 158 | perhaps because you are placing that project under version control for |
| 157 | 159 | the first time: |
| 158 | 160 | |
| 159 | 161 | cd long-established-project |
| @@ -182,11 +184,11 @@ | ||
| 182 | 184 | purposes of this example. |
| 183 | 185 | |
| 184 | 186 | We’ve drawn this example to create a tight parallel between Fossil and |
| 185 | 187 | Git, not to commend this `.fsl`-at-project-root trick to you. A better |
| 186 | 188 | choice would be `~/museum/home/long-established-project.fossil`, if |
| 187 | -you’re following the directory scheme exemplified above. That said, it | |
| 189 | +you’re following [the directory scheme exemplified above](#rname). That said, it | |
| 188 | 190 | does emphasize an earlier point: Fossil doesn’t care where you put the |
| 189 | 191 | repo DB file or what you name it. |
| 190 | 192 | |
| 191 | 193 | |
| 192 | 194 | [clone]: /help?cmd=clone |
| 193 | 195 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -114,23 +114,23 @@ | |
| 114 | [cw]: ./ckout-workflows.md |
| 115 | |
| 116 | |
| 117 | #### <a id="close" name="dotfile"></a> Closing A Check-Out |
| 118 | |
| 119 | The `fossil close` command dissaociates a check-out directory from the |
| 120 | Fossil repository database, nondestructively inverting `fossil open`. It |
| 121 | won’t remove the managed files, and unless you give the `--force` |
| 122 | option, it won’t let you close the check-out with uncommitted changes to |
| 123 | those managed files. |
| 124 | |
| 125 | The `close` command also refuses to run without `--force` when you have |
| 126 | certain precious per-checkout data, which Fossil stores in the |
| 127 | `.fslckout` file at the root of a check-out directory. This is a SQLite |
| 128 | database that keeps track of local state such as what version you have |
| 129 | checked out, the contents of the [stash] for that working directory, the |
| 130 | [undo] buffers, per-checkout [settings][set], and so forth. The stash |
| 131 | and undo buffers are considered precious, being “uncommitted changes,” |
| 132 | so you have to force Fossil to discard these as part of closing the |
| 133 | check-out. |
| 134 | |
| 135 | Thus, `.fslckout` is not the same thing as `.git`! |
| 136 | |
| @@ -137,23 +137,25 @@ | |
| 137 | In native Windows builds of Fossil — that is, excluding Cygwin and WSL |
| 138 | builds, which follow POSIX conventions — this file is called `_FOSSIL_` |
| 139 | instead to get around the historical 3-character extension limit with |
| 140 | certain legacy filesystems. |
| 141 | |
| 142 | Closing a check-out directory is a rare operation. One common use case |
| 143 | is that you’re about to delete it, so you want Fossil to forget about it |
| 144 | for the purposes of commands like [`fossil all`][all]. |
| 145 | |
| 146 | The closest equivalent for `fossil close` in Git is |
| 147 | `git worktree remove`. |
| 148 | |
| 149 | [all]: /help?cmd=all |
| 150 | |
| 151 | |
| 152 | #### <a id="iip"></a> Init In Place |
| 153 | |
| 154 | To illustrate these differences, consider this common Git “init in place” |
| 155 | method for creating a new repository from an existing tree of files, |
| 156 | perhaps because you are placing that project under version control for |
| 157 | the first time: |
| 158 | |
| 159 | cd long-established-project |
| @@ -182,11 +184,11 @@ | |
| 182 | purposes of this example. |
| 183 | |
| 184 | We’ve drawn this example to create a tight parallel between Fossil and |
| 185 | Git, not to commend this `.fsl`-at-project-root trick to you. A better |
| 186 | choice would be `~/museum/home/long-established-project.fossil`, if |
| 187 | you’re following the directory scheme exemplified above. That said, it |
| 188 | does emphasize an earlier point: Fossil doesn’t care where you put the |
| 189 | repo DB file or what you name it. |
| 190 | |
| 191 | |
| 192 | [clone]: /help?cmd=clone |
| 193 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -114,23 +114,23 @@ | |
| 114 | [cw]: ./ckout-workflows.md |
| 115 | |
| 116 | |
| 117 | #### <a id="close" name="dotfile"></a> Closing A Check-Out |
| 118 | |
| 119 | The [`fossil close`][close] command dissaociates a check-out directory from the |
| 120 | Fossil repository database, nondestructively inverting [`fossil open`][open]. It |
| 121 | won’t remove the managed files, and unless you give the `--force` |
| 122 | option, it won’t let you close the check-out with uncommitted changes to |
| 123 | those managed files. |
| 124 | |
| 125 | The `close` command refuses to run without `--force` when you have |
| 126 | certain precious per-checkout data, which Fossil stores in the |
| 127 | `.fslckout` file at the root of a check-out directory. This is a SQLite |
| 128 | database that keeps track of local state such as what version you have |
| 129 | checked out, the contents of the [stash] for that working directory, the |
| 130 | [undo] buffers, per-checkout [settings][set], and so forth. The stash |
| 131 | and undo buffers are considered precious uncommitted changes, |
| 132 | so you have to force Fossil to discard these as part of closing the |
| 133 | check-out. |
| 134 | |
| 135 | Thus, `.fslckout` is not the same thing as `.git`! |
| 136 | |
| @@ -137,23 +137,25 @@ | |
| 137 | In native Windows builds of Fossil — that is, excluding Cygwin and WSL |
| 138 | builds, which follow POSIX conventions — this file is called `_FOSSIL_` |
| 139 | instead to get around the historical 3-character extension limit with |
| 140 | certain legacy filesystems. |
| 141 | |
| 142 | Closing a check-out directory is a rare operation. One use case |
| 143 | is that you’re about to delete the directory, so you want Fossil to forget about it |
| 144 | for the purposes of commands like [`fossil all`][all]. Even that isn’t |
| 145 | necessary, because Fossil will detect that this has happened and forget |
| 146 | the working directory for you. |
| 147 | |
| 148 | The closest equivalent in Git is `git worktree remove`. |
| 149 | |
| 150 | [all]: /help?cmd=all |
| 151 | |
| 152 | |
| 153 | #### <a id="iip"></a> Init In Place |
| 154 | |
| 155 | To illustrate the differences that Fossil’s separation of repository |
| 156 | from working directory creates in practice, consider this common Git “init in place” |
| 157 | method for creating a new repository from an existing tree of files, |
| 158 | perhaps because you are placing that project under version control for |
| 159 | the first time: |
| 160 | |
| 161 | cd long-established-project |
| @@ -182,11 +184,11 @@ | |
| 184 | purposes of this example. |
| 185 | |
| 186 | We’ve drawn this example to create a tight parallel between Fossil and |
| 187 | Git, not to commend this `.fsl`-at-project-root trick to you. A better |
| 188 | choice would be `~/museum/home/long-established-project.fossil`, if |
| 189 | you’re following [the directory scheme exemplified above](#rname). That said, it |
| 190 | does emphasize an earlier point: Fossil doesn’t care where you put the |
| 191 | repo DB file or what you name it. |
| 192 | |
| 193 | |
| 194 | [clone]: /help?cmd=clone |
| 195 |