/[meta-cvs]/meta-cvs/F-F1216688DF5C31C04736DBD403342A77
ViewVC logotype

Contents of /meta-cvs/F-F1216688DF5C31C04736DBD403342A77

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.5 - (hide annotations)
Thu Jan 31 05:35:02 2002 UTC (12 years, 2 months ago) by kaz
Branch: MAIN
CVS Tags: mcvs-0-3, mcvs-0-6, mcvs-0-9, mcvs-0-2, mcvs-0-5, mcvs-0-4, mcvs-0-7, mcvs-0-8, latest-patch
Changes since 1.4: +27 -27 lines
MCVS is being renamed to Meta-CVS.
1 kaz 1.5 A Quick Guide to Using Meta-CVS
2 kaz 1.1
3     Kaz Kylheku
4     January 25, 2002
5    
6 kaz 1.3 "Anything you can do, I can do meta." -- origin unknown
7    
8 kaz 1.1
9     Contents
10    
11 kaz 1.3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . Line 15
12     2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13     3. Filtering F- Names to Readable Names . . . . . . . . . . . . 63
14 kaz 1.1
15     1. Introduction
16    
17 kaz 1.5 This is a guide toward using Meta-CVS. It assumes familiarity with
18 kaz 1.1 version control concepts and in particular with the CVS software.
19 kaz 1.5 In particular, it is assumed that you have hands-on experience
20     with CVS and that you have read the Cederqvist manual.
21 kaz 1.1
22 kaz 1.5 In principle, Meta-CVS could be understood as a version control
23 kaz 1.1 tool independently of CVS; in practice it helps to know CVS,
24 kaz 1.5 particularly because Meta-CVS is relatively new software, and
25     because it is not intended to perfectly hide CVS from the user.
26 kaz 1.1
27 kaz 1.5 It is also assumed that you have successfully installed Meta-CVS.
28 kaz 1.1 For installation instructions see the file INSTALL.
29    
30 kaz 1.5 To gain some understanding of how Meta-CVS represents your data
31     and how it works, read Meta-CVS-PAPER.
32 kaz 1.1
33    
34     2. Overview
35    
36 kaz 1.5 Meta-CVS has a command syntax that is deliberately similar to the
37     CVS command syntax. In general, a Meta-CVS command looks like
38 kaz 1.1 this:
39    
40     mcvs [ mcvs-options ] command [ command-options ] [ arguments ]
41    
42     Most of the options are simply passed through to CVS, when
43     appropriate. So for example,
44    
45 kaz 1.4 mcvs -z 3 update -A
46 kaz 1.1
47 kaz 1.4 will pass through the -z 3 and -A options down to CVS when invoking
48 kaz 1.1 it, so that CVS ends up being called as:
49    
50 kaz 1.4 cvs -z 3 update -A
51 kaz 1.1
52 kaz 1.5 This passing through of options makes it easy to use Meta-CVS for
53 kaz 1.1 users who are familiar with CVS, and is also straightforward to
54 kaz 1.5 deal with in the bowels of Meta-CVS.
55 kaz 1.1
56     Not all options are passed through to CVS, and there are some that
57 kaz 1.5 are entirely Meta-CVS-specific. Think of Meta-CVS as implementing
58     an intelligent filter over the CVS options. For example, if you
59 kaz 1.1 invoke ``mcvs --help'', you don't want ``cvs --help'' to be
60     called. [TODO: intelligent filtering not implemented yet.]
61 kaz 1.2
62    
63     3. Filtering F- Names to Readable Names
64    
65 kaz 1.5 The Meta-CVS representation brings a readability problem: the
66     cryptic F- names appear in the output produced by CVS, making it
67     difficult to understand what file the output pertains to. For
68     this reason, Meta-CVS includes a filtering command (``mcvs filt'')
69     which can be used in a pipe to filter out the cryptic names and
70     replace them with the paths that they map to. For example:
71 kaz 1.2
72     mcvs diff | mcvs filt
73    
74     produces a human-readable diff.
75    
76 kaz 1.5 The filter works by looking for character sequences consisting of
77     the prefix ``F-'' followed by exactly 32 hex digits. If such a
78     sequence is mapped in the MAP-LOCAL file, then it is replaced by
79     its mapping. Anything which doesn't match or doesn't map is passed
80     through unchanged.

  ViewVC Help
Powered by ViewVC 1.1.5