Fossil SCM

Expanded the "timeline is the log" section of gitusers.md with info from this forum post: https://www.fossil-scm.org/forum/forumpost/e891cce862

wyoung 2020-11-01 19:16 trunk
Commit c8b414ab8db3f24fa207594611ec3beda680214c18d3d7f2631333d06d73da9d
1 file changed +36 -6
+36 -6
--- www/gitusers.md
+++ www/gitusers.md
@@ -164,21 +164,51 @@
164164
[undo]: /help?cmd=undo
165165
166166
167167
## <a id="log"></a> Fossil’s Timeline is the “Log”
168168
169
-Git users often need to use the `git log` command to grovel through
169
+Git users often need to use the `git log` command to dig linearly through
170170
commit histories due to its [weak data model][wdm].
171171
172172
Fossil parses a huge amount of information out of commits that allow it
173
-to produce its [timeline CLI][tlc] and [its `/timeline` web view][tlw],
173
+to produce its [timeline CLI][tlc] and [its `/timeline` web view][tlw]
174
+using indexed SQL lookups,
174175
which generally have the info you would have to manually extract from
175
-`git log`.
176
+`git log`, produced much more quickly than Git can.
176177
177
-[tlc]: /help?cmd=timeline
178
-[tlw]: /help?cmd=/timeline
179
-[wdm]: ./fossil-v-git.wiki#durable
178
+Unlike Git’s log, Fossil’s timeline shows info across branches by
179
+default, a feature for maintaining better situational awareness. The
180
+`fossil timeline` command has no way to show a single branch’s commits,
181
+but you can restrict your view like this using the web UI equivalent by
182
+clicking the name of a branch on the `/timeline` or `/brlist` page. (Or
183
+manually, by adding the `r=` query parameter.) Note that even in this
184
+case, the Fossil timeline still shows other branches where they interact
185
+with the one you’ve referenced in this way; again, better situational
186
+awareness.
187
+
188
+If you truly need a backwards-in-time-only view of history in Fossil to
189
+emulate `git log`, this is as close as you can currently come:
190
+
191
+ fossil timeline parents current
192
+
193
+Again, though, this isn’t restricted to a single branch, as `git log`
194
+is.
195
+
196
+Another useful rough equivalent is:
197
+
198
+ git log --raw
199
+ fossil time -v
200
+
201
+This shows what changed in each version, though Fossil’s view is more a
202
+summary than a list of raw changes. To dig deeper into single commits,
203
+you can use Fossil’s [`info` command][infoc] or its [`/info` view][infow].
204
+
205
+[infoc]: /help?cmd=info
206
+[infow]: /help?cmd=/info
207
+[tlc]: /help?cmd=timeline
208
+[tlw]: /help?cmd=/timeline
209
+[wdm]: ./fossil-v-git.wiki#durable
180210
181211
182212
<a id="staging"></a>
183213
## There Is No Staging Area
184214
185215
--- www/gitusers.md
+++ www/gitusers.md
@@ -164,21 +164,51 @@
164 [undo]: /help?cmd=undo
165
166
167 ## <a id="log"></a> Fossil’s Timeline is the “Log”
168
169 Git users often need to use the `git log` command to grovel through
170 commit histories due to its [weak data model][wdm].
171
172 Fossil parses a huge amount of information out of commits that allow it
173 to produce its [timeline CLI][tlc] and [its `/timeline` web view][tlw],
 
174 which generally have the info you would have to manually extract from
175 `git log`.
176
177 [tlc]: /help?cmd=timeline
178 [tlw]: /help?cmd=/timeline
179 [wdm]: ./fossil-v-git.wiki#durable
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
180
181
182 <a id="staging"></a>
183 ## There Is No Staging Area
184
185
--- www/gitusers.md
+++ www/gitusers.md
@@ -164,21 +164,51 @@
164 [undo]: /help?cmd=undo
165
166
167 ## <a id="log"></a> Fossil’s Timeline is the “Log”
168
169 Git users often need to use the `git log` command to dig linearly through
170 commit histories due to its [weak data model][wdm].
171
172 Fossil parses a huge amount of information out of commits that allow it
173 to produce its [timeline CLI][tlc] and [its `/timeline` web view][tlw]
174 using indexed SQL lookups,
175 which generally have the info you would have to manually extract from
176 `git log`, produced much more quickly than Git can.
177
178 Unlike Git’s log, Fossil’s timeline shows info across branches by
179 default, a feature for maintaining better situational awareness. The
180 `fossil timeline` command has no way to show a single branch’s commits,
181 but you can restrict your view like this using the web UI equivalent by
182 clicking the name of a branch on the `/timeline` or `/brlist` page. (Or
183 manually, by adding the `r=` query parameter.) Note that even in this
184 case, the Fossil timeline still shows other branches where they interact
185 with the one you’ve referenced in this way; again, better situational
186 awareness.
187
188 If you truly need a backwards-in-time-only view of history in Fossil to
189 emulate `git log`, this is as close as you can currently come:
190
191 fossil timeline parents current
192
193 Again, though, this isn’t restricted to a single branch, as `git log`
194 is.
195
196 Another useful rough equivalent is:
197
198 git log --raw
199 fossil time -v
200
201 This shows what changed in each version, though Fossil’s view is more a
202 summary than a list of raw changes. To dig deeper into single commits,
203 you can use Fossil’s [`info` command][infoc] or its [`/info` view][infow].
204
205 [infoc]: /help?cmd=info
206 [infow]: /help?cmd=/info
207 [tlc]: /help?cmd=timeline
208 [tlw]: /help?cmd=/timeline
209 [wdm]: ./fossil-v-git.wiki#durable
210
211
212 <a id="staging"></a>
213 ## There Is No Staging Area
214
215

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button