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
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
|
<HTML>
<HEAD>
<TITLE>CvsGui : MacCVS and WinCvs: Summary of CvsGui commands</TITLE>
</HEAD>
<BODY>
<A HREF="cvsgui-3.html"><IMG SRC="prev.gif" ALT="Previous"></A>
<A HREF="cvsgui-5.html"><IMG SRC="next.gif" ALT="Next"></A>
<A HREF="cvsgui.html#toc4"><IMG SRC="toc.gif" ALT="Contents"></A>
<HR>
<H2><A NAME="s4">4. Summary of CvsGui commands</A></H2>
<H2><A NAME="ss4.1">4.1 <B>Cvs Main</B> menu</A></H2>
<P>Main cvs commands : Most of the time you will use only the update and commit commands.</P>
<P>
<A NAME="HID_APP_UPDATE"></A>
</P>
<H3>Update folder...</H3>
<P>Merge recursively on your disk your changes with the cvs repository. Use "Commit folder..."
to commit your changes INTO the cvs repository.</P>
<P>
<A NAME="HIDD_COMMIT_MAIN"></A>
<A NAME="HID_APP_COMMIT"></A>
</P>
<H3>Commit folder...</H3>
<P>Commit your changes INTO the cvs repository. You may use "Update folder..." first to merge
locally on your disk your changes with the cvs repository.</P>
<P>The <B>no recursive</B> option let you commit a folder without the sub-folders.</P>
<P>
<A NAME="HID_APP_PREFERENCES"></A>
</P>
<H3>Preferences...</H3>
<P>Use this option to change settings like the CVSROOT, the read-only option,
the TCP/IP compression and many other things...</P>
<P>
<A NAME="HIDD_CMDLINE_MAIN"></A>
<A NAME="HID_APP_CMDLINE"></A>
</P>
<H3>Command line...</H3>
<P>Allows to enter a cvs command line (like "cvs rtags -b -r arev arevbranch") when
ever the cvs command is not available thru the menus.</P>
<P>Note that you don't have necessary to specify a local directory. That's because
some commands (like rtags) execute only on the server. For the most of the
others commands, you need to specify <B>where</B> the command is executed.</P>
<P>
<A NAME="HIDD_CHECKOUT_MAIN"></A>
<A NAME="HID_APP_CHECKOUT"></A>
</P>
<H3>Checkout module...</H3>
<P>Use this option to checkout from scratch a new module on your disk. You need
to give the complete path of the module on the server : for example :
"myprog/mysubfolder1/mysubfolder2"</P>
<P>The <B>no recursive</B> option let you commit a folder without the sub-folders.</P>
<P>
<A NAME="HIDD_IMPORT_MAIN"></A>
<A NAME="HIDD_IMPORT_TAGS"></A>
<A NAME="HID_APP_IMPORT"></A>
</P>
<H3>Import module...</H3>
<P>Use this option to create a new module into the cvs repository located on the
cvs server machine. After importing, you should use the "Checkout module..."
command to start using this new module.</P>
<P>You need to give the complete path of the module on the server : for example :
"myprog/mysubfolder1/finalPlaceForTheModule"</P>
<P>Refer to the explanation of the import problem (
<A HREF="cvsgui-2.html#import">Mac import</A> or
<A HREF="cvsgui-3.html#winimport">Windows import</A>).</P>
<P>The <B>vendor</B> and <B>release</B> tags are usefull whenever you'll want to get
back to the initial version or create a branch. Refer to the cvs documentation
for more details.</P>
<P>
<A NAME="HID_APP_LOGIN"></A>
</P>
<H3>Login...</H3>
<P>Use this option when you want to login for the first time to a cvs server machine.
You should need to login ONLY if the kind of authentication in the preferences
is "pserver" (password authenticate).</P>
<H2><A NAME="ss4.2">4.2 <B>Cvs Files</B> menu</A></H2>
<P>Menu with cvs commands which apply on files.</P>
<P>
<A NAME="HID_APP_UPDATEF"></A>
</P>
<H3>Update files...</H3>
<P>Merge locally on your disk your changes and the changes of the cvs repository so
you can use the "Commit files..." command to commit your change on the cvs server
repository.</P>
<P>
<A NAME="HID_APP_COMMITF"></A>
</P>
<H3>Commit files...</H3>
<P>Commit your changes into the cvs server repository. You may need first to
"Update files..." in order to merge your changes with the cvs server before
you can commit them.</P>
<P>
<A NAME="HID_APP_DIFF"></A>
</P>
<H3>Diff files...</H3>
<P>Show the difference between your files and the files located on the cvs
server repository : this way you can check the changes with the remote server.</P>
<P>
<A NAME="HID_APP_LOG"></A>
</P>
<H3>Log files...</H3>
<P>Ask the server to tell the history of the files (comments, revision number,
tags and so on...)</P>
<P>
<A NAME="HID_APP_ADDF"></A>
</P>
<H3>Add files...</H3>
<P>Mark the files to be added to the master repository located on the server.
These files will be really added AFTER you did commit them. In order to
add files enclosed into a new folder, use the "Add folder..." option first
on the folder.</P>
<P>
<A NAME="HID_APP_ADDB"></A>
(Windows only)</P>
<H3>Add binary files...</H3>
<P>Same as the previous but add binary files.</P>
<P>
<A NAME="HID_APP_REMOVEF"></A>
</P>
<H3>Remove files...</H3>
<P>Mark the files to be removed from the master repository located on the
server. These files will be really removed AFTER you did commit the folder
where these files were located.</P>
<P>
<A NAME="HID_APP_STATUS"></A>
</P>
<H3>Status files...</H3>
<P>Ask the cvs server to tell the status of the files (changed locally,
unchanged, current status, locks, and so on...).</P>
<P>
<A NAME="HID_APP_CANCELC"></A>
</P>
<H3>Cancel changes...</H3>
<P>It is not a real cvs command but it's provided for convenience.
This option will send to trash the files in the trash (you can
on Macintosh use the "Put Away" option of the Finder to recover them) then
will ask the cvs server to update these files.</P>
<H2><A NAME="ss4.3">4.3 <B>Cvs Folder</B> menu</A></H2>
<P>The cvs commands which apply on a folder.</P>
<P>
<A NAME="HID_APP_ADD"></A>
</P>
<H3>Add a folder...</H3>
<P>Whenever you add files to the repository, you need first to add the folders.</P>
<P>
<A NAME="HID_APP_DIFFF"></A>
</P>
<H3>Diff a folder...</H3>
<P>Print the differences recursively with the cvs remote repository for all the
files enclosed in the folder.</P>
<P>
<A NAME="HIDD_PREFS_CVSROOT"></A>
<A NAME="HIDD_PREFS_GLOBALS"></A>
<A NAME="HIDD_PREFS_PORTS"></A>
</P>
<H2><A NAME="ss4.4">4.4 <B>Preferences</B> dialog</A></H2>
<P>The cvs commands which apply on a folder.</P>
<P>
<A NAME="HIDC_CVSROOT"></A>
</P>
<H3>The CVSROOT field</H3>
<P>It should be something like alexp@cvs.strata3d.com:/cvsroot.
Never enter the ":pserver:" or ":kserver:" directly, use the
radio buttons instead.</P>
<P>
<A NAME="HIDC_CHECKOUTRO"></A>
</P>
<H3>Checkout read-only</H3>
<P>Turn-on if you want the files created by MacCVS to appear
locked in the finder.</P>
<P>
<A NAME="HIDC_PRUNE"></A>
</P>
<H3>Prune empty directories</H3>
<P>If On, this option will automatically remove empty folders
when you update a module.</P>
<P>
<A NAME="HIDC_TCPIP"></A>
</P>
<H3>TCP/IP compression</H3>
<P>When this option is on, the server and MacCVS compress informations
so they use less bandwidth : use only if you have a slow (modem)
connection with the server because it causes the server to work
much more.</P>
<P>
<A NAME="HIDC_QUIET"></A>
</P>
<H3>Quiet mode</H3>
<P>If on, cause the command to be somewhat quiet; informational messages,
such as reports of recursion through subdirectories, are
suppressed.</P>
<P>
<A NAME="HIDC_CTNLADD"></A>
</P>
<H3>Control when adding files</H3>
<P>Most of the errors using cvs are related to binary files. Since the client and the server usually <B>convert</B> the line feeds, it's important when you add a file to specify if you add a binary file <B>or</B> a text file. This option will help you to not make errors by parsing the file you add and check if it's a binary file, if the file has the good line feed for the machine and so on...</P>
<P>
<A NAME="HIDC_RHOSTS"></A>
</P>
<H3>".rhosts" authentication</H3>
<P>If On, the cvs server will authenticate MacCVS regarding the IP number
of the machine running MacCVS : you should have a proper ".rhosts" file
on the server account with an access 0600 which contains something like
"192.10.10.37 alexp" or "alexpmac.strata3d.com alexp".</P>
<P>
<A NAME="HIDC_PSERVER"></A>
</P>
<H3>":pserver:" authentication</H3>
<P>If On, the cvs server will authenticate MacCVS regarding a password
located in the cvs administration file "passwd" on the server :
you should have a proper entry for you in this file, something like
"alexp:X5gFtdhaDke93j".</P>
<P>
<A NAME="HIDC_KSERVER"></A>
</P>
<H3>":kserver:" authentication</H3>
<P>If On, the cvs server will authenticate MacCVS regarding a Kerberos
authentication session. Refer to your adminstrator to know how to use
Kerberos.</P>
<H3>Modify the server ports & name</H3>
<P>Regarding the authentication you use (pserver, kserver...) you can change
the default TCP <B>ports and name</B> cvs uses to reach the server. Refer to the cvs
documentation for more details.</P>
<H3>ISO8559 translation on text files (Mac only)</H3>
<P>If on, MacCvs will translate (only on text files) the mac characters encoding
into a standard ISO8559_xxx encoding when it sends the file <B>to</B> the server. It
will obviously translate back ISO8559_xxx characters encoding into the Mac encoding
when getting a file <B>from</B> the server. This option is usefull if you use
accentuations in text files because the accents will remain readable on
others systems (Windows, Unix). Only ISO8559_1 Latin 1 (Western Europe) is
implemented right now. Thanks to Jim Matthews to provide the ISO8559_1 table
in the <B>Fetch</B> program.</P>
<H3>Use Internet Config for text files (Mac only)</H3>
<P>MacCvs usually asks <B>Internet Config</B>, whenever it creates a <B>binary</B> file,
the default <B>type and creator</B> signature for the file. So by using
Internet Config, you can tell MacCvs that, for example, all the files
ending by the extension .mcp have the file type/creator set to MMPr/CWIE.
By using this option, you can extend this behaviour to the <B>text</B> files so you
can for example map a type/creator for the .c, .h, .html...</P>
<P>
<A NAME="dirtyfiles"></A>
</P>
<HR>
<A HREF="cvsgui-3.html"><IMG SRC="prev.gif" ALT="Previous"></A>
<A HREF="cvsgui-5.html"><IMG SRC="next.gif" ALT="Next"></A>
<A HREF="cvsgui.html#toc4"><IMG SRC="toc.gif" ALT="Contents"></A>
</BODY>
</HTML>
|
