Fossil SCM
With the changes introduced in [213ca339c2951ad1] it is now possible to restrict the timeline to a single branch also with "fossil timeline".
Commit
abb54cb0cf1ee96f9028787498fa85413dd027f8399a33b724fd676eb3642d5e
Parent
fdd8057dffd866d…
1 file changed
+5
-5
+5
-5
| --- www/gitusers.md | ||
| +++ www/gitusers.md | ||
| @@ -300,15 +300,15 @@ | ||
| 300 | 300 | Yet the constants are *not* equal because Fossil |
| 301 | 301 | reads from a single disk file rather than visit potentially many |
| 302 | 302 | files in sequence as Git must, so the OS’s buffer cache can result in |
| 303 | 303 | [still better performance][35pct]. |
| 304 | 304 | |
| 305 | -Unlike Git’s log, Fossil’s timeline shows info across branches by | |
| 306 | -default, a feature for maintaining better situational awareness. Although the | |
| 307 | -`fossil timeline` command has no way to show a single branch’s commits, | |
| 308 | -you can restrict your view like this using the web UI equivalent by | |
| 309 | -clicking the name of a branch on the `/timeline` or `/brlist` page. (Or | |
| 305 | +Unlike Git’s log, Fossil’s timeline shows info across all branches by | |
| 306 | +default, a feature for maintaining better situational awareness. | |
| 307 | +It is possible to restrict the timeline to a single branch using `fossil timeline -b`. | |
| 308 | +Similarly, to restrict the timeline using the web UI equivalent, | |
| 309 | +click the name of a branch on the `/timeline` or `/brlist` page. (Or | |
| 310 | 310 | manually, by adding the `r=` query parameter.) Note that even in this |
| 311 | 311 | case, the Fossil timeline still shows other branches where they interact |
| 312 | 312 | with the one you’ve referenced in this way; again, better situational |
| 313 | 313 | awareness. |
| 314 | 314 | |
| 315 | 315 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -300,15 +300,15 @@ | |
| 300 | Yet the constants are *not* equal because Fossil |
| 301 | reads from a single disk file rather than visit potentially many |
| 302 | files in sequence as Git must, so the OS’s buffer cache can result in |
| 303 | [still better performance][35pct]. |
| 304 | |
| 305 | Unlike Git’s log, Fossil’s timeline shows info across branches by |
| 306 | default, a feature for maintaining better situational awareness. Although the |
| 307 | `fossil timeline` command has no way to show a single branch’s commits, |
| 308 | you can restrict your view like this using the web UI equivalent by |
| 309 | clicking the name of a branch on the `/timeline` or `/brlist` page. (Or |
| 310 | manually, by adding the `r=` query parameter.) Note that even in this |
| 311 | case, the Fossil timeline still shows other branches where they interact |
| 312 | with the one you’ve referenced in this way; again, better situational |
| 313 | awareness. |
| 314 | |
| 315 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -300,15 +300,15 @@ | |
| 300 | Yet the constants are *not* equal because Fossil |
| 301 | reads from a single disk file rather than visit potentially many |
| 302 | files in sequence as Git must, so the OS’s buffer cache can result in |
| 303 | [still better performance][35pct]. |
| 304 | |
| 305 | Unlike Git’s log, Fossil’s timeline shows info across all branches by |
| 306 | default, a feature for maintaining better situational awareness. |
| 307 | It is possible to restrict the timeline to a single branch using `fossil timeline -b`. |
| 308 | Similarly, to restrict the timeline using the web UI equivalent, |
| 309 | click the name of a branch on the `/timeline` or `/brlist` page. (Or |
| 310 | manually, by adding the `r=` query parameter.) Note that even in this |
| 311 | case, the Fossil timeline still shows other branches where they interact |
| 312 | with the one you’ve referenced in this way; again, better situational |
| 313 | awareness. |
| 314 | |
| 315 |