Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Mention the "worktree" git command in the Fossil-versus-Git document. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
af91e0575e4293a931253fc7e8403e10 |
| User & Date: | drh 2019-01-28 20:59:45 |
Context
|
2019-02-01
| ||
| 15:55 | Update the built-in SQLite to the latest 3.27.0 alpha. check-in: 6ba52d79 user: drh tags: trunk | |
|
2019-01-29
| ||
| 15:02 | Merge trunk check-in: 7843b1c6 user: jan.nijtmans tags: openssl-1.1 | |
|
2019-01-28
| ||
| 20:59 | Mention the "worktree" git command in the Fossil-versus-Git document. check-in: af91e057 user: drh tags: trunk | |
| 19:59 | Markdownism fixes in previous check-in: 39825691 user: wyoung tags: trunk | |
Changes
Changes to www/fossil-v-git.wiki.
178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 |
Fossil says that the unix philosophy is "it just works". Both
individuals have written their DVCSes to reflect their own view
of the "unix philosophy".
<h3>2.6 One vs. Many Check-outs per Repository</h3>
A "repository" in Git is a pile-of-files in the ".git" subdirectory
of a single check-out. The check-out and the repository are inseperable.
With Fossil, a "repository" is a single SQLite database file
that can be stored anywhere. There
can be multiple active check-outs from the same repository, perhaps
open on different branches or on different snapshots of the same branch.
Long-running tests or builds can be running in one check-out while
changes are being committed in another.
<h3>2.7 What you should have done vs. What you actually did</h3>
Git puts a lot of emphasis on maintaining
a "clean" check-in history. Extraneous and experimental branches by
individual developers often never make it into the main repository. And
branches are often rebased before being pushed, to make
it appear as if development had been linear. Git strives to record what
|
| > > > > > > > > > |
178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 |
Fossil says that the unix philosophy is "it just works". Both individuals have written their DVCSes to reflect their own view of the "unix philosophy". <h3>2.6 One vs. Many Check-outs per Repository</h3> A "repository" in Git is a pile-of-files in the ".git" subdirectory of a single check-out. The check-out and the repository are located together in the filesystem. With Fossil, a "repository" is a single SQLite database file that can be stored anywhere. There can be multiple active check-outs from the same repository, perhaps open on different branches or on different snapshots of the same branch. Long-running tests or builds can be running in one check-out while changes are being committed in another. (Update 2019-01-29:) The check-out and the repository in Git used to be inseparable. More recently, Git has been enhanced with the "[https://git-scm.com/docs/git-worktree|worktree]" command that allows a single repository to host multiple check-outs. However, the interface is sufficiently difficult to use that most people find it easier to create a separate clone for each check-out. <h3>2.7 What you should have done vs. What you actually did</h3> Git puts a lot of emphasis on maintaining a "clean" check-in history. Extraneous and experimental branches by individual developers often never make it into the main repository. And branches are often rebased before being pushed, to make it appear as if development had been linear. Git strives to record what |