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
|
<html>
<head>
<title>The arch Archive Format</title>
</head>
<body>
<a name="The_arch_Archive_Format"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>The arch Archive Format</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
<b>prev: </b><a href="patch-set-format.html#The_arch_Patch_Set_Format">The arch Patch Set Format</a></br>
</small>
<br>
<p><a name="index-pt:0"></a>
</p><p>An arch archive is a directory containing a number of files and
subdirectories. Its structure is described in this appendix.
</p>
<a name="Directory_Structure"></a>
<h3 align=center>Directory Structure</h3>
<p>Each category, branch, version, and revision are given a separate
directory. These are nested. From the root of the archive:
</p><pre>
CATEGORY/
CATEGORY/BRANCH/
CATEGORY/BRANCH/VERSION/
CATEGORY/BRANCH/VERSION/REVISION/
</pre>
<p>For example, version <code>1.0</code>
of the <code>devo</code>
branch of the <code>arch</code>
category
might have these directories:
</p><pre>
arch/
arch/arch--devo/
arch/arch--devo--1.0/
arch/arch--devo--1.0/base-0/ # the base revision
arch/arch--devo--1.0/patch-1/ # pre-patch revisions
arch/arch--devo--1.0/patch-2/ # ...
...
arch/arch--devo--1.0/version-0/ # the version revision
arch/arch--devo--1.0/versionfix-1/ # post-patch revisions
arch/arch--devo--1.0/versionfix-2/ # ...
...
</pre>
<a name="Within_a_Revision_Directory"></a>
<h3 align=center>Within a Revision Directory</h3>
<p>Every revision directory contains the log message for that revision as
a plain-text file:
</p><p><strong><u>File:</u></strong>
log
</p><p><strong><u>Format:</u></strong>
RFC822-style headers plus body
</p><p>If a revision directory is a full-source revision (typically a
<code>base-0</code>
revision) it will contain a compressed tar file of the entire
revision tree. The name of the tar file is the full name (sans
archive name) of the revision:
</p><p><strong><u>File:</u></strong>
REVISION.tar.gz
</p><p><strong><u>Format:</u></strong>
gzip-compressed tar file containing a complete source tree,
rooted in a single top-level directory named REVISION.
</p><p><strong><u>Example:</u></strong>
arch--devo--1.0--base-0.tar.gz
</p><pre>
contains a full-source tree rooted at
`arch--devo--1.0--base-0'
</pre>
<p>If a revision directory is a patch (not a full-source revision), then
the revision directory contains a compressed tar file of the patch
set (see <a href="patch-set-format.html#The_arch_Patch_Set_Format">The arch Patch Set Format</a>):
</p><p><strong><u>File:</u></strong>
REVISION.patches.tar.gz
</p><p><strong><u>Format:</u></strong>
gzip-compressed tar file containing a patch set, rooted in a
single top-level directory named REVISION.
</p><p><strong><u>Example:</u></strong>
arch--devo--1.0--patch-1.tar.gz
</p><pre>
contains a patch-set tree rooted at `arch--devo--1.0--patch-1'
</pre>
<p><strong><u>Note:</u></strong> Every revision is either a full source revision or a patch
revision. Thus, every revision directory contains exactly one of the
two files:
</p><pre>
REVISION.tar.gz
REVISION.patches.tar.gz
</pre>
<p>If a revision is a continuation revision (a tag of some other revision)
</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>
|
