41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
determines which version of the documentation to display.
Fossil provides a variety of ways to specify a check-in. This
document describes the various methods.
<h2>Canonical Check-in Name</h2>
The canonical name of a checkin is the SHA1 hash of its
[./fileformat.wiki#manifest | manifest] expressed as a 40-character
lowercase hexadecimal number. For example:
<blockquote><pre>
fossil info e5a734a19a9826973e1d073b49dc2a16aa2308f9
</pre></blockquote>
|
|
|
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
determines which version of the documentation to display.
Fossil provides a variety of ways to specify a check-in. This
document describes the various methods.
<h2>Canonical Check-in Name</h2>
The canonical name of a check-in is the SHA1 hash of its
[./fileformat.wiki#manifest | manifest] expressed as a 40-character
lowercase hexadecimal number. For example:
<blockquote><pre>
fossil info e5a734a19a9826973e1d073b49dc2a16aa2308f9
</pre></blockquote>
|
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
The "tag:deed2" name will refer to the most recent check-in
tagged with "deed2" not to the
check-in whose canonical name begins with "deed2".
<h2>Whole Branches</h2>
Usually when a branch name is specified, it means the latest checkin on
that branch. But for some commands (ex: [/help/purge|purge]) a branch name
on the argument means the earliest connected checkin on the branch. This
seems confusing when being explained here, but it works out to be intuitive
in practice.
For example, the command "fossil purge XYZ" means to purge the checkin XYZ
and all of its descendants. But when XYZ is in the form of a branch name, one
generally wants to purge the entire branch, not just the last checkin on the
branch. And so for this reason, commands like purge will interpret a branch
name to be the first checkin of the branch rather than the last. If there
are two or more branches with the same name, then these commands will select
the first check-in of the branch that has the most recent checkin. What
happens is that Fossil searches for the most recent checkin with the given
tag, just as it always does. But if that tag is a branch name, it then walks
back down the branch looking for the first check-in of that branch.
Again, this behavior only occurs on a few commands where it make sense.
<h2>Timestamps</h2>
|
|
|
|
|
|
|
|
|
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
The "tag:deed2" name will refer to the most recent check-in
tagged with "deed2" not to the
check-in whose canonical name begins with "deed2".
<h2>Whole Branches</h2>
Usually when a branch name is specified, it means the latest check-in on
that branch. But for some commands (ex: [/help/purge|purge]) a branch name
on the argument means the earliest connected check-in on the branch. This
seems confusing when being explained here, but it works out to be intuitive
in practice.
For example, the command "fossil purge XYZ" means to purge the check-in XYZ
and all of its descendants. But when XYZ is in the form of a branch name, one
generally wants to purge the entire branch, not just the last check-in on the
branch. And so for this reason, commands like purge will interpret a branch
name to be the first check-in of the branch rather than the last. If there
are two or more branches with the same name, then these commands will select
the first check-in of the branch that has the most recent check-in. What
happens is that Fossil searches for the most recent check-in with the given
tag, just as it always does. But if that tag is a branch name, it then walks
back down the branch looking for the first check-in of that branch.
Again, this behavior only occurs on a few commands where it make sense.
<h2>Timestamps</h2>
|