39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
-
+
-
-
|
<a name="q3"></a>
<p><b>(3) How do I create a new branch?</b></p>
<blockquote>There are lots of ways:
When you are checking in a new change using the <b>[/help/commit|commit]</b>
command, you can add the option "--branch <i>BRANCH-NAME</i>" to
make the new check-in be the first check-in for a new branch. You can
make the new check-in be the first check-in for a new branch.
also add the "--bgcolor <i>COLOR</i>" option to give the branch a
specific background color on timelines.
|
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
-
+
+
+
|
<a name="q4"></a>
<p><b>(4) How do I tag a check-in?</b></p>
<blockquote>There are several ways:
When you are checking in a new change using the <b>[/help/commit|commit]</b>
command, you can add a tag to that check-in using the
"--tag <i>TAGNAME</i>" command-line option.
"--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag
option to give a check-in multiple tags. Tags need not be unique. So,
for example, it is common to give every released version a "release" tag.
If you want add a tag to an existing check-in, you can use the
<b>[/help/tag|tag]</b> command. For example:
<blockquote>
<b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i>
</blockquote>
|