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

Diff of /meta-cvs/F-F1216688DF5C31C04736DBD403342A77

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.7 by kaz, Sun Jun 23 19:18:11 2002 UTC revision 1.8 by kaz, Sun Jul 28 02:17:08 2002 UTC
# Line 99  Line 99 
99    
100        2. Invoke        2. Invoke
101    
102             mcvs create <module-name> <vendor-tag> <release-tag>             mcvs create <module-name> <release-tag>
103    
104           The <module-name> specifies what your module will be called; it           The <module-name> specifies what your module will be called; it
105           need not be the same as the name of the top level directory.           need not be the same as the name of the top level directory.
106           When later you check out the module, you will have to specify that           When later you check out the module, you will have to specify that
107           name, and by default a directory of that name will be created.           name, and by default a directory of that name will be created.
108    
109           The <vendor-tag> and <release-tag> are artifacts of cvs import,           The <release-tag> is a symbolic revision that is applied to
110           which is the command that Meta-CVS uses to create the CVS repository for the           the newly created file revisions; it will come in handy if
111           new project. These arguments must be specified. The vendor-tag is used           you ever have to refer to this original baseline.
          by CVS to tag the vendor branch on which the import takes place. The  
          release-tag tags all the newly imported file revisions.  
112    
113     (!)   Note that CVS vendor branches do not work in Meta-CVS;     (!)   Note that CVS vendor branches do not work in Meta-CVS;
114           each mcvs create operation creates a new unique set of files, so doing           each mcvs create operation creates a new unique set of files, so doing
115           multiple imports over the same Meta-CVS module will *not* work like it           multiple imports over the same Meta-CVS module will *not* work like it
116           does in CVS. As a workaround, if you want to synchronize with third           does in CVS. Do not ever run mcvs create on the same module.
117           party sources, you can do so manually using ordinary branches.           Meta-CVS has a feature that is superior to CVS vendor branches;
118             this feature is the ``mcvs grab'' command, which takes a snapshot
119             of code onto a normal branch, and handles renamed files.
120    
121        3. If your file tree contains any files whose names have suffixes,        3. If your file tree contains any files whose names have suffixes,
122           Meta-CVS will gather a list of these suffixes and bring up a text           Meta-CVS will gather a list of these suffixes and bring up a text

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.5