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
|
<html>
<head>
<title>A Very Brief Overview of arch</title>
</head>
<body>
<a name="A_Very_Brief_Overview_of_arch"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>A Very Brief Overview of arch</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
</small>
<br>
<p>If you understand <code>mkpatch</code>
and <code>dopatch</code>
, the rest of <code>arch</code>
is
conceptually simple.
</p><p><code>arch</code>
lets you build a library of revisions of a source tree.
</p><p>You can use the command <code>larch get</code>
to retrieve a particular revision,
and then make changes to your local copy.
</p><p>You can use the command <code>larch commit</code>
to store your modified revision
in the archive. <code>commit</code>
compares your modifed revision to the
original using <code>mkpatch</code>
. It converts the patch set to a compressed
tar file and installs that tar file in the archive (along with a log
message).
</p><p>In ordinary use, when you <code>get</code>
a revision, <code>arch</code>
finds some "full
source" revision, then applies any patches necessary to get the
revision you asked for. <code>arch</code>
uses <code>dopatch</code>
for that.
</p><p><code>arch</code>
organizes revisions into "development paths" -- successive
revisions, each one patch away from the previous.
</p><p>You can form a "branches" -- places where one development path
splits into two distinct paths.
</p><p>You can perform various kinds of "merge" -- selectively applying
various patches to bring your working copies up-to-date with respect
to one or more development paths.
</p><p>When multiple people share an archive, they use it as a "rendezvous
point" -- a place and mechanism for sharing and coordinating patch
sets.
</p><p><code>arch</code>
"decorates" your source trees with some control files. The
most important of these form the "patch log" -- a record of all of
the patches that have been applied to your tree. The patch log helps
users by forming a detailed record of the changes that have been made
(similar to, but more accurate than, the <code>ChangeLog</code>
many programmers
maintain by hand). The patch log helps <code>arch</code>
when it comes time to
merge: <code>arch</code>
uses the log to decide which patches to apply, and which
to skip.
</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>
|
