Fossil SCM

Update documentation: check-in name 'start:' can be chained as well.

danield 2023-06-30 07:28 trunk
Commit 36adf66b78762754bcd9bbfe47135941dca43f2ebda4eed39ebd59c83cd14577
1 file changed +2 -2
--- www/checkin_names.wiki
+++ www/checkin_names.wiki
@@ -238,12 +238,12 @@
238238
any changes that have already been merged in from the parent branch.
239239
240240
<a id="start"></a>
241241
The prefix "<tt>start:</tt>" gives the first check-in of the named branch.
242242
243
-The prefixes "<tt>root:</tt>" and "<tt>merge-in:</tt>" can be chained: one
244
-can say for example
243
+The prefixes "<tt>root:</tt>", "<tt>start:</tt>", and "<tt>merge-in:</tt>"
244
+can be chained: one can say for example
245245
246246
<blockquote><tt>
247247
fossil info merge-in:xyzzy:2022-03-01
248248
</tt></blockquote>
249249
250250
--- www/checkin_names.wiki
+++ www/checkin_names.wiki
@@ -238,12 +238,12 @@
238 any changes that have already been merged in from the parent branch.
239
240 <a id="start"></a>
241 The prefix "<tt>start:</tt>" gives the first check-in of the named branch.
242
243 The prefixes "<tt>root:</tt>" and "<tt>merge-in:</tt>" can be chained: one
244 can say for example
245
246 <blockquote><tt>
247 fossil info merge-in:xyzzy:2022-03-01
248 </tt></blockquote>
249
250
--- www/checkin_names.wiki
+++ www/checkin_names.wiki
@@ -238,12 +238,12 @@
238 any changes that have already been merged in from the parent branch.
239
240 <a id="start"></a>
241 The prefix "<tt>start:</tt>" gives the first check-in of the named branch.
242
243 The prefixes "<tt>root:</tt>", "<tt>start:</tt>", and "<tt>merge-in:</tt>"
244 can be chained: one can say for example
245
246 <blockquote><tt>
247 fossil info merge-in:xyzzy:2022-03-01
248 </tt></blockquote>
249
250

Keyboard Shortcuts

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