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
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>F.2.CVS Tree Organization</title>
<link rel="stylesheet" href="stylesheet.css" type="text/css">
<link rev="made" href="pgsql-docs@postgresql.org">
<meta name="generator" content="DocBook XSL Stylesheets V1.70.0">
<link rel="start" href="index.html" title="PostgreSQL 8.1.4 Documentation">
<link rel="up" href="cvs.html" title="AppendixF.The CVS Repository">
<link rel="prev" href="cvs.html" title="AppendixF.The CVS Repository">
<link rel="next" href="cvsup.html" title="F.3.Getting The Source Via CVSup">
<link rel="copyright" href="ln-legalnotice.html" title="Legal Notice">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="cvs-tree"></a>F.2.<span class="productname">CVS</span> Tree Organization</h2></div></div></div>
<p> </p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Author</h3>
<p> Written by Marc G. Fournier (<code class="email"><<a href="mailto:scrappy@hub.org">scrappy@hub.org</a>></code>) on 1998-11-05
</p>
</div>
<p>
</p>
<p> The command <code class="command">cvs checkout</code> has a flag, <code class="option">-r</code>,
that lets you check out a
certain revision of a module. This flag makes it easy to, for example,
retrieve the
sources that make up release 6_4 of the module `tc' at any time in the
future:
</p>
<pre class="programlisting">cvs checkout -r REL6_4 tc</pre>
<p>
This is useful, for instance, if someone claims that there is a bug in
that release, but you cannot find the bug in the current working copy.
</p>
<div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Tip</h3>
<p> You can also check out a module as it was at any given date using the
<code class="option">-D</code> option.
</p>
</div>
<p>
</p>
<p> When you tag more than one file with the same tag you can think
about the tag as “<span class="quote">a curve drawn through a matrix of filename vs.
revision number</span>”. Say we have 5 files with the following revisions:
</p>
<pre class="programlisting"> file1 file2 file3 file4 file5
1.1 1.1 1.1 1.1 /--1.1* <-*- TAG
1.2*- 1.2 1.2 -1.2*-
1.3 \- 1.3*- 1.3 / 1.3
1.4 \ 1.4 / 1.4
\-1.5*- 1.5
1.6
</pre>
<p>
then the tag <code class="literal">TAG</code> will reference
file1-1.2, file2-1.3, etc.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p> For creating a release branch, other than a
<code class="literal">-b</code> option added to the command, it's the same thing.</p>
</div>
<p>
</p>
<p> So, to create the 6.4 release
I did the following:
</p>
<pre class="programlisting">cd pgsql
cvs tag -b REL6_4</pre>
<p>
which will create the tag and the branch for the RELEASE tree.
</p>
<p> For those with <span class="productname">CVS</span> access, it's simple to
create directories for different versions.
First, create two subdirectories, RELEASE and CURRENT, so that you don't
mix up the two. Then do:
</p>
<pre class="programlisting">cd RELEASE
cvs checkout -P -r REL6_4 pgsql
cd ../CURRENT
cvs checkout -P pgsql</pre>
<p>
which results in two directory trees, <code class="filename">RELEASE/pgsql</code> and
<code class="filename">CURRENT/pgsql</code>. From that point on,
<span class="productname">CVS</span>
will keep track of which repository branch is in which directory tree, and will
allow independent updates of either tree.
</p>
<p> If you are <span class="emphasis"><em>only</em></span> working on the <code class="literal">CURRENT</code>
source tree, you just do
everything as before we started tagging release branches.
</p>
<p> After you've done the initial checkout on a branch
</p>
<pre class="programlisting">cvs checkout -r REL6_4</pre>
<p>
anything you do within that directory structure is restricted to that
branch. If you apply a patch to that directory structure and do a
</p>
<pre class="programlisting">cvs commit</pre>
<p>
while inside of it, the patch is applied to the branch and
<span class="emphasis"><em>only</em></span> the branch.
</p>
</div></body>
</html>
|
