1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
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
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
|
<html>
<head>
<title>Development Paths</title>
</head>
<body>
<a name="Development_Paths"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>Development Paths</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
<b>next: </b><a href="basic-rc.html#Basic_Revision_Control">Basic Revision Control</a></br>
<b>prev: </b><a href="archives.html#Archives">Archives</a></br>
</small>
<br>
<p>An <code>arch</code>
archive is organized around <em>
<a name="index-pt:0"></a>
development paths
</em>
. Each
development path is a succession of revisions, each (usually)
differing from the previous revision by a simple patch.
</p><p>Every development path has a project name with version number, such
as:
</p><pre>
hello--devo--1.0
</pre>
<p>Project names were previously discussed (see <a href="project-names.html#The_arch_Global_Name-space_of_Projects">The arch Global Name-space of Projects</a>).
</p><p>As we'll see in the next chapter, each development path is further
subdivided into specific revisions, each having a <em>
<a name="index-pt:1"></a>
patch level name
</em>
,
as in these examples:
</p><pre>
hello--devo--1.0--patch-3
hello--devo--1.0--patch-4
hello--devo--1.0--patch-5
</pre>
<a name="Creating_a_Development_Path"></a>
<h3 align=center>Creating a Development Path</h3>
<p><a name="index-pt:2"></a>
<a name="index-pt:3"></a>
<a name="index-pt:4"></a>
</p><p>Supposing that you have set your default archive, you can create a new
development path in three steps:
</p><pre>
% larch make-category CATEGORY-NAME
</pre>
<pre>
% larch make-branch BRANCH-NAME
</pre>
<pre>
% larch make-version VERSION-NAME
</pre>
<p>as in this example that creates the version <code>hello--devo--1.0</code>
:
</p><pre>
% larch make-category hello
% larch make-branch hello--devo
% larch make-version hello--devo--1.0
</pre>
<p>and this example that creates <code>hello--1.0</code>
:
</p><pre>
% larch make-category hello
% larch make-branch hello
% larch make-version hello--1.0
</pre>
<p>Note that in the second example, the branch label is empty.
</p>
<a name="Examining_an_Archive"></a>
<h3 align=center>Examining an Archive</h3>
<p><a name="index-pt:5"></a>
<a name="index-pt:6"></a>
<a name="index-pt:7"></a>
</p><p>You can review what's in an archive using the commands:
</p><pre>
% larch categories
- print a list of categories
</pre>
<pre>
% larch branches CATEGORY-NAME
- print a list of branches within a category
</pre>
<pre>
% larch versions BRANCH-NAME
-print a list of versions within a branch
</pre>
<a name="Fully_Qualified_Version_Names"></a>
<h3 align=center>Fully Qualified Version Names</h3>
<p><a name="index-pt:8"></a>
<a name="index-pt:9"></a>
</p><p>Every version is associated with a particular archive. Ordinarilly,
if you write a simple version name, your default archive is presumed.
However, wherever a version name is called for, you can use a <em>
<a name="index-pt:10"></a>
fully
qualified version name
</em>
of the form:
</p><pre>
ARCHIVE-NAME/VERSION-NAME
</pre>
<p>as in the example:
</p><pre>
joe.hacker@gnu.org--test-archive/hello--devo--1.0
</pre>
<p>That can be useful when operating on a remote archive that is not your
default archive. For example, you could use the name in the example
to retrieve the latest revision from Joe Hacker's archive, in
preparation for creating a branch of that version in your local
archive.
</p>
<small><i>arch: The arch Revision Control System
</i></small><br>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
</body>
|
