ViewVC logotype

Contents of /meta-cvs/F-B3689DBB46386B16F4B2331934B69223

Parent Directory Parent Directory | Revision Log Revision Log

Revision - (show annotations)
Wed Jul 16 15:44:11 2003 UTC (10 years, 9 months ago) by kaz
Branch: mcvs-1-0-branch
Changes since +6 -0 lines
* code/mcvs-generic.lisp (mcvs-generic): Removed
the default-include-meta-files keyword parameter.
(mcvs-tag, mcvs-commit): Remove use of keyword parameter.
This fixes the silly behavior of including meta files
even when the command line specifies a file list.
Also, bugfix: *nometa-option* now works when
global-if-empty-file-list is true, and there are no files.

* code/update.lisp (mcvs-update): Remove use of keyword
parameter in call to mcvs-generic.
1 Release Notes for Meta-CVS
3 Release 1.0.9, 2003-0?-??:
5 Failures to open terminal for reasons other than non-existence
6 of the object are handled (e.g. ``no such device'', etc).
8 The --nometa option now works properly in those commands that
9 operate on the whole project when no file arguments are given
10 (tag, update, commit). Also, these commands no longer implicitly
11 include the meta files when file arguments *are* given.
12 These files can be included explicitly with the --meta global option.
14 Release 1.0.8, 2003-06-03:
16 The Cygwin /dev/tty problem is partially addressed. The program
17 won't fail if /dev does not exist, but emits a warning message,
18 and disables interactive error handling. The workaround is to use
19 ``mkdir /dev''. This is a CLISP issue; its OPEN function expects the
20 full path to a file to actually exist, but on Cygwin, there are fake
21 /dev/* paths even though /dev does not exist. If a real /dev directory
22 does in fact exist, it does not interfere with these magic paths.
24 The ``mcvs fi'' command no longer performs expansion on F- names
25 that are preceded by a slash.
27 Release 1.0.7, 2003-04-23:
29 New commands sync-to-cvs and sync-from-cvs expose the hard link
30 synchronization algorithm.
32 Revamped error recovery logic. To continue in an error situation now
33 consistently means ``take the bold action that may erase data''
34 or ``proceed in the most obvious way to finish the specified job''.
35 It never means ``roll back the operation and bail'', which was
36 confusing.
38 Termination is no longer unsafe; the `T' menu command, and the
39 equivalent --error-terminate global option perform all necessary
40 restoration and cleanup.
42 Errors that have more information to print, like a list of files or
43 whatever, now indicate it in a standard way which translates to the
44 `I' menu command.
46 Chatter output goes to standard error rather than standard output,
47 as do all error messages.
49 The interactive error menu now talks to the user using the controlling
50 tty, meaning that it will work even if the input or output of the
51 mcvs command are redirected. If no controlling tty is available,
52 then interactive error handling is disabled; the default behavior
53 is then like --error-terminate but can of course be overridden by
54 --error-continue.
56 Release 1.0.6, 2003-04-14:
58 The create command detects the existence of text editor backup files (or
59 other junk) in the MCVS directory after the editor is invoked on the
60 TYPES file. The user is prompted regarding their removal. If these files are
61 not removed, cvs import will bring them into the repository.
63 When Meta-CVS has to split a large CVS command into two or more
64 invocations with shorter argument lists, it now does not stop when one of
65 these invocations is unsuccessful; it does all of them, and combines
66 their termination indications by a logical AND. There was a bug in this
67 logic also which caused, upon termination failure, a cvs command to be
68 repeated for the same list of files.
70 Synchronization logic has been revamped. Unnecessary synchronizations
71 have been removed, which will make some commands run faster.
72 Synchronizations now have specific directions; for instance before
73 a CVS commit or update, changes are pushed from the directory tree to the MCVS
74 directory only, and after the CVS operation, in the reverse direction only.
76 Meta-CVS will no longer re-create missing F- files by linking from the
77 directory tree. Doing this causes two problems. One is that if a user
78 manually removes a F- file and do ``mcvs up'', she wants CVS to fetch a clean
79 copy and push it into the tree. She does not want the file to be restored
80 from the tree prior to the CVS update. Secondly, sometimes CVS itself
81 removes files. If we re-create the files, CVS will consider them to
82 be ``in the way''.
84 Failures to read from the MAP or MAP-LOCAL files are treated as interactive,
85 continuable errors. By continuing, the user agrees that the behavior will
86 be as if an empty map were read.
88 The grab command uses less memory for performing move analysis.
90 Release 1.0.5, 2003-02-25:
92 Bugfix: some one-argument command line options of CVS must be
93 specifies as a single parameter, with no separation between the
94 option letter and the argument characters. For example:
96 cvs log -r rev-1::rev-2 # invalid
97 cvs log -rrev1::rev2 # correct
99 Meta-CVS accepts either syntax, but it was generating the first form
100 when calling CVS. Now, *all* one-letter options that have an argument
101 are formatted in the second manner.
103 Bugfix: one more waitpid() issue was fixed; on fast machines, under
104 Linux, it was observed that from time to time Meta-CVS would get
105 a -1/ECHILD when waiting for the CVS process.
107 Release 1.0.4, 2003-02-20:
109 Fix remaining occurences of the CVS ``No child processes'' abort
110 problem, affecting the list-branches command, merge command
111 and the -r option of the filt command.
113 Release 1.0.3, 2003-02-12:
115 ! THIS RELEASE IS WITHDRAWN. It was accidentally created from the
116 ! experimental main trunk of the Meta-CVS codebase, rather than
117 ! the 1.0 branch. But 1.0.4 does contain all of the changes
118 ! described here.
120 Fix for the CVS ``No child processes'' abort problem. It turns out
121 that CLISP sets the signal handling action for the SIGCHLD signal
122 to SIG_IGN, which is inherited by child processes across the
123 fork() and execvp() calls used in our mcvs_spawn() function.
124 We correct the problem by resetting the signal handler to SIG_DFL
125 just before executing the new process image.
127 New feature, --up option. The argument is a nonnegative integer value
128 (default is zero) which specifies how many sandbox nesting levels to
129 escape out of when locating the sandbox root. This helps work with
130 nested Meta-CVS sandboxes.
132 Release 1.0.2, 2003-02-10:
134 Bugfix in waitpid logic in the C library for running external processes;
135 we were not dealing with an interrupted waitpid.
137 Behavior of mcvs tag is changed: when there are no filename arguments,
138 the whole tree is tagged including the metafiles. In other words, it
139 now works like the commit command.
141 Release 1.0.1, 2003-01-30:
143 Hard link sync optimization: update of a subset of files, commit, and
144 other operations like log and diff don't need to synchronize all
145 hard links, just the ones operated on.
147 The merge and remerge commands support -k option for overriding
148 CVS keyword expansion mode.
150 Fixes to getcwd error handling.
152 Improvement in install.sh script's logic for locating CLISP installation
153 directory.
155 Release 1.0, 2003-01-01:
157 NOTE: It's not possible to upgrade to this release via mcvs-upgrade,
158 because it adds some new C functions to the Lisp executable.
160 Security fix: read-time evaluation was not suppressed when reading
161 structured data, like MCVS/MAP and MCVS/TYPES. This means that it
162 was possible for Alice to check in something that would execute
163 arbitrary code on Bob's computer.
165 Optimization: use fork and exec to launch CVS rather than CLISP's
166 run-program function, which indirects through the shell interpreter.
167 (On Cygwin, the spawnvp function is used).
169 Performance fix: stat() was being called superfluously by the
170 hard synchronization code, twice for each file.
172 Build fix: install.sh works when CLISP executable is called ``lisp.exe'',
173 which is the case under Cygwin with newer CLISP releases.
175 Release 0.99, 2002-11-17:
177 New link command for creating symbolic links.
179 Global option -n (dry run---don't modify filesystem) is processed
180 internally now, not just passed to CVS.
182 Failure to invoke text editor is handled.
184 The -r option of filt is fixed; it has been broken since the change to the
185 new MAP format, because it was reading the raw map representation, not
186 passing it through the right conversion steps that are needed now.
188 Bugfix to purge and remap commands: they were fooled by CVS-generated
189 files in the MCVS/CVS directory. Specifically, files having F- names, and a
190 the suffix ,t.
192 Bugfix to add logic in directory restructuring: there was the possibility
193 of mistakingly taking a clobbered local file to be a new local version of
194 the added file, instead of replacing it. This could happen if the local
195 file had a future timestamp relative to the one coming from the repository.
197 The prop command does not synchronize or write out map if no options are
198 specified.
200 Help text added for move and branch commands. Help text for grab rewritten.
202 The CVSEDITOR and VISUAL environment variables are now checked, not
203 only EDITOR.
205 Release 0.98, 2002-10-13:
207 The prop command was mistakenly reading from MAP-LOCAL and writing to MAP,
208 which could cause information loss if the two differ. It now reads from MAP
209 and writes to MAP. (The property changes propagate to MAP-LOCAL by the
210 update operation invoked by prop, as before).
212 Invocation of external programs included in debug trace.
214 The filt command does not filter F- names if they are immediately preceded by
215 the MCVS/ prefix; such occurences are clearly concrete, sandbox-relative
216 references to the actual F- links, rather than abstract references.
218 The update command now supports the -C option, to fetch the repository
219 copy, throwing away local changes. It also now honors the --metaonly
220 and --nometa options.
222 The export command has been added, for checking out documents without creating
223 a working copy (no MCVS directory in the root of the checkout).
225 The watch command has been added. Note that its syntax differs from that
226 of CVS.
228 The watchers, editors, edit, and unedit commands have been added.
230 A script called mcvs-upgrade is now included, and installs alongside the mcvs
231 script. This allows the Meta-CVS Lisp image to recompile and patch itself,
232 giving users of binary distributions an easy way to upgrade from source
233 code.
235 Release 0.97, 2002-10-06:
237 Meta-CVS now builds and runs on Microsoft Windows, under Cygwin
238 (www.cygwin.com). It still relies on hard links, which requires
239 Windows 2000 or XP, and the NTFS filesystem. It probably won't
240 work over FAT.
242 New --debug option for verbose output.
244 Cleaned up of error messages. Error messages don't specify prefixes like
245 ``mcvs-add:'' or ``mcvs-grab:'' any more. Rather, the error handler adds the
246 ``mcvs:'' prefix when printing the messages in a situation when the error is
247 not continuable.
249 Fixed bug introduced in release 0.13: mcvs add -R was adding only
250 directories, effectively ignoring arguments that are regular files.
251 The error-continuation behavior of mcvs add has been revised.
253 Trying to rename an object onto itself, or to move the sandbox root
254 directory are no longer silent no-ops, but produce an error.
256 The remap command now preserves property lists, and picks up changes
257 in executable permission.
259 The grab command now notices when a file changes from having execute
260 permission to not having execute permission.
262 Operations on the path . now work in a partial sandbox.
264 Release 0.96, 2002-09-21:
266 The restore command was left broken during the change to the new
267 filemap format. It is now fixed.
269 The grab command now handles execute permission bits properly.
271 Some more commands have detailed help.
273 There is now a global option -i which specifies a script to be
274 executed. This allows Meta-CVS to be scripted using Lisp. For
275 instance suppose you have the following script and call it
276 list-matching:
278 #!/usr/local/bin/mcvs -i
279 (in-sandbox-root-dir
280 (let ((mapping (mapping-read *mcvs-map*))
281 (test-func (eval (read-from-string (pop *args*)))))
282 (dolist (entry mapping)
283 (with-slots (path raw-plist) entry
284 (when (funcall test-func raw-plist)
285 (format t "~a~%" path))))))
287 Then to list the names of files whose "importance" property is
288 a value greater than two, run:
290 ./list-matching '(lambda (plist)
291 (let ((imp (getf plist :importance)))
292 (and imp (> imp 2))))'
294 WARNING: Scripting accesses the guts of Meta-CVS directly, so scripts may
295 break as Meta-CVS is maintained. There is currently no published set of
296 stable interfaces.
298 Release 0.95, 2002-09-16:
300 The install.sh script no longer uses a borrowed copy of the clisp-link script
301 or the linkkit directory; these have been removed. These materials
302 are available at every CLISP installation; install.sh now finds them
303 and uses them. Users of non-x86 machines ran into problems because of this
304 because linkkit/clisp.h contains architecture-dependent information.
306 A bug in mcvs filt was fixed; it wasn't handling F- names that aren't found
307 in the map.
309 A more detailed help system now exists, though it's not complete. The ``mcvs
310 help'' command acts just like ``mcvs --help'' without any arguments. If given
311 an additional parameter which specifies a Meta-CVS command, it produces more
312 detailed documentation for that comand. Help exists already for a few
313 commands.
315 The release number is being warped to 0.95, which means that Meta-CVS is now
316 in beta. It is only five updates away from a 1.0 release.
318 Release 0.24, 2002-09-08:
320 The mapping entries for both symlinks and files have extensible property
321 lists now. These are stored in the optional fourth and fifth list elements,
322 respectively of the :FILE and :SYMLINK map entries.
324 Versioning of the execute permission of files is supported, represented as
325 the :EXEC property of a :FILE mapping entry.
327 Some lame syntax is provided for manipulating properties:
329 mcvs prop --set foo --clear bar --remove baz main.c list.c
331 will set the property FOO to true, set the property BAR to false,
332 and remove the property BAZ, in the files main.c and list.c.
333 The execute permission is represented by the property EXEC.
335 Release 0.23, 2002-09-02:
337 Bugfix: the grab command notices edited symlinks and incorporates the
338 changes into the mapping.
340 The grab command now figures out moved symlinks. Moved symlinks are those
341 whose pathname has changed, but which continue to point to the same object
342 (which may also have been moved).
344 Release 0.22, 2002-08-31:
346 Symbolic links are now versioned objects. The format of the MAP file
347 changes to accomodate this; the new Meta-CVS will read old MAP
348 files; when it writes it will write the new format. Old Meta-CVS won't
349 read the new format.
351 When a new module is created from an existing file tree, symbolic
352 links will be recognized and added. The add command will also add
353 symbolic links. Symbolic links can be renamed and moved; this does
354 nothing with their contents. They can point outside of the sandbox
355 using relative or absolute paths.
357 TODO:
359 There doesn't exist yet a special command to create symbolic links, nor to
360 retarget them; retargetting a link can be done manually by editing MCVS/MAP
361 and updating. Retargetting a link using the ln -s command, won't
362 backpropagate to the MAP file; an update will clobber the link.
364 The grab command does not yet compute symbolic link moves; a moved symbolic
365 link is treated as a remove and add. This will be easy to fix.
367 The remap command ignores symlinks.
369 Release 0.21, 2002-08-04:
371 Syntax of grab command changed. The branch is no longer specified as an
372 argument, but using the -r command option. If no revision is specified with
373 -r, then a -A must be specified to make the grab go to the main trunk. This
374 is a safety feature, since grabbing foreign snapshots to the trunk is almost
375 always wrong, though it could be useful during backup recovery, or for fixing
376 mistakes.
378 The way operating system functions are targetted has changed. Instead of
379 relying on the ``linuxlibc6'' module provided by CLISP, Meta-CVS now
380 has its own module for calling foreign functions. This module is portable;
381 it does not depend on the layout of glibc data structures. So Meta-CVS
382 is in theory now portable to other Unixes (provided they have /dev/urandom).
384 Release 0.20, 2002-07-27:
386 The commit command does a true global commit when given no file or directory
387 parameters, and not given the --metaonly option. This means commiting all
388 changes in the MCVS directory, even if they are in F-files that are not
389 currently mapped.
391 Release 0.19, 2002-07-16:
393 When moving multiple files or directories to a subdirectory, a
394 restart is now provided to skip over bad ones and continue.
396 Grab no longer scans files if there are only added files, or only removed
397 files. There are no moves to deduce in that case.
399 Restore properly creates lost+found at the root of a partial sandbox,
400 rather than at the abstract root of the module.
402 Some other algorithmic improvements made.
404 The first few sections of a user guide have been written.
406 Release 0.18, 2002-07-07:
408 Cool new feature: checkout takes an extra argument, which specifies a
409 subdirectory of the project. Specifying a subdirectory results in a ``partial
410 sandbox'', whose root directory is the specified subdirectory of the larger
411 project. The rest of the project is ``invisible'' to that sandbox. A
412 subdirectory argument can also be given to mcvs grab, which will cause it to
413 integrate the new source tree against a subtree of the Meta-CVS project
414 rather than the entire project. The subtree doesn't have to exist; in
415 that case you get an empty sandbox. Adding files to this sandbox will cause
416 the tree to exist in the project.
418 Bugfix: mcvs grab was not computing moves properly over small file sets,
419 wrongly treating them as removes and adds.
421 Release 0.17, 2002-07-02:
423 The create command no longer takes a vendor branch. Instead the symbol
424 ``Created-by-Meta-CVS'' is used as the vendor tag to satisfy CVS.
426 The grab command no longer does useless synchronization on files that
427 are about to be deleted.
429 New purge command; does ``cvs rm'' on deleted files, that is to say, F- files
430 that have no mapping.
432 New restore command; re-enters deleted files into the mapping, under
433 the ``lost+found'' directory, using their F- names as sandbox names.
435 Bugfix: when a checkout bails because it is requested over top of an existing
436 working copy, it must not delete that working copy's MCVS sub directory.
438 Release 0.16, 2002-06-29:
440 Added new heuristics to grab command. Paths are analyzed to determine
441 move distance. Greater distances reduce the confidence in a move.
442 These rules help sort out grabs in a project where similar or
443 duplicate files are subject to parallel moves, the ambiguity being
444 resolved by favoring shorter moves. Word comparisons are case-insensitive
445 now. Common words (those that appear in many files) are ignored when
446 comparing files.
448 New options, --meta and --metaonly. This area of Meta-CVS is cleaned
449 up a little bit. Most reporting commands like log or diff no longer
450 operate on meta files by default; they must be explicitly told to do
451 so with --meta or --metaonly. Only the commit command implicitly includes
452 metafiles by default, and so if this is not wanted, --nometa must be
453 selected. The update command remains special; if it is given file
454 arguments, it does not include meta files. If given no arguments, it
455 does a global CVS up across the entire project.
457 Release 0.15, 2002-06-25:
459 Optimized a string splitting routine which is used heavily for processing
460 paths; the result is a noticeable performance improvement in some commands
461 that process large numbers of files.
463 Renamed ``import'' command to ``create''.
465 Bugfix: checkout and create showed errors when removing directory, due to
466 broken :postorder support in directory walking function.
468 Bugfix: on failure, checkout was failing to delete the MCVS directory when
469 the checkout was directed to an existing directory.
471 New feature: ``mcvs grab'' command imports third-party snapshots to a
472 branch. This is invoked in the root directory of the source tree to import.
473 It determines what files have been added and removed in the snapshot, and
474 tries to compute which removes and adds are actually moves. This is done by
475 analyzing the actual contents of the files according to a crude algorithm to
476 do fuzzy comparisons, so that even files which were modified as well as moved
477 are discovered.
479 Release 0.14, 2002-06-21:
481 Bugfix: mcvs add was broken for files that have no suffix, causing
482 the underlying cvs add to fail. This was broken in 0.7 when type
483 handling was added.
485 Release 0.13, 2002-06-06:
487 Sandbox synchronization now handles the case of two files having
488 the same timestamp. An error is signaled, with interactive resolution
489 to synchronize either way, or do nothing.
491 If a file must be deleted on update, and this cannot be done, it
492 is now a continuable error.
494 Bugfix: pass -I ! to cvs import so that it won't ignore some F- files
495 whose suffix is one of the ones cvs ignores by default.
497 New command: mcvs remap. The user can move or delete files directly without
498 going through Meta-CVS. When mcvs remap is invoked, it will hunt down the
499 moves and deletions, and reconstruct the mapping accordingly; that is,
500 it remaps the new structure. This command uses inode numbers to identify
501 files; if a file is copied and then the original is deleted, that won't
502 be recognized as a move.
504 Release 0.12, 2002-04-18:
506 Bugfix: remove was broken in 0.10, fixed now.
508 Bugfix: status, diff, etc. work in empty project rather than complaining
509 ``. not known to Meta-CVS''.
511 The checkout operation now can now populate an existing directory, including
512 the current working directory (mcvs co -d . modulename). Of course, the
513 target directory cannot be an existing Meta-CVS sandbox.
514 This is a useful feature, which allows sandboxes to blend with an
515 existing directory structure.
517 Checkout now uses the same function for generating the sandbox
518 structure as does update. This is now necessary, because local files
519 can be clobbered by the checkout.
521 Release 0.11, 2002-04-12:
523 Bugfix: when branch invokes rtag, it now takes the CVSROOT information
524 from CVS/Root and passes it via -d. This is necessary because rtag does not
525 look at a local CVS subdirectory for this information, only the
526 -d option or the environment variable.
528 Command for listing branches added (list-branches or lb). Also shows
529 what sticky tag the sandbox is updated to.
531 Command for switching branches added (switch or sw).
533 Merge detects that working copy is on non-branch tag and bails.
535 Absolute paths can now be specified as file arguments. These are
536 based from the root directory of the sandbox, not the actual filesystem root
537 directory.
539 Release 0.10, 2002-04-03:
541 Automatic merging implemented. Branch is created using branch command,
542 and merging from another branch is done using simple merge command.
543 Meta-CVS maintains the tags to keep track of what has been merged
544 from what branch to what branch.
546 Bugfix: checkout -d foo bar was complaining about directory bar already
547 existing, even though it should only care about foo.
549 The remove command now requires explicit -R option to recursively remove
550 a directory. It has more detailed error reporting.
552 The move command has better error reporting.
554 Release 0.9, 2002-03-14:
556 Bugfix: the .cvsignore file is now subject to tagging, status, etc,
557 (unless --nometa is specified, of course).
559 The mcvs filt command takes -r <revision> or -D <date> parameters.
560 This means to retrieve the MAP file as of the specified revision or
561 date and use that mapping to perform the filtering translation,
562 rather than using MAP-LOCAL.
564 The mcvs update command takes filename arguments now and also
565 supports the -p option.
567 Release 0.8, 2002-03-13:
569 Bug fixed in mcvs add; it was not ignoring files that are already
570 listed as :ignore in MCVS/TYPES.
572 Bug fixed in mcvs move: a target with a trailing slash is now treated
573 as a directory (if it does not already exist and is a non-directory).
575 The -d option of mcvs checkout can now be used to override the checkout
576 directory, which is normally the same as the module name.
578 The global options --version, --help, -q, -Q and -e are now supported.
580 New global options --error-continue and --error-terminate to disable
581 interactive error handling in two different ways.
583 Log level of many messages has changed; many messages have been
584 relegated to debug level.
586 The import command now creates a .cvsignore file containing the name
589 Release 0.7, 2002-03-09:
591 The import command collects a list of the file suffixes and brings up
592 a text editor to allow the user to edit their CVS keyword expansion
593 behavior. This information is kept in a new metafile called TYPES. The
594 add command also updates TYPES; it identifies any suffixes which are new,
595 and brings up an editor. The F- files now carry suffixes, which
596 simplifies interfacing with CVS, and also allows cvswrappers to work.
598 Recursive add works (mcvs add -R ...).
600 New command line option --nometa allows metafiles to be excluded from
601 diff, tag, and other commands; without the option they are inserted
602 into the list of files to be processed.
604 The commit option now takes an optional list of files or directories,
605 just like tag, diff, and others.
607 Release 0.6, 2002-02-16:
609 The add operation was horribly broken in 0.5, it is fixed.
611 User can interactively select whether to clobber local files or leave
612 everything alone. Effects on the mapping file of a mcvs move are undone,
613 if the restructuring is rolled back, or raises a condition that leads
614 to termination.
616 Meta-CVS now keeps a new meta-file called MCVS/TYPES. This is created
617 during import, and specifies the CVS keyword expansion mode for files
618 having given suffixes, and can also tell Meta-CVS to ignore certain files
619 when importing or adding.
621 Release 0.5, 2002-02-10:
623 Much improved error handling. Filesystem rearranging code performs
624 sanity checks to prevent adds and moves from accidentally clobbering
625 local files. A rearranging gone bad can be rolled back. Effects
626 of a failed mcvs add can also be rolled back.
628 MAP-LOCAL is now sorted in the same way as MAP.
630 Release 0.4, 2002-02-04:
632 CVS is invoked using internal function resembling the xargs utility,
633 which ensures that multiple command lines are generated if necessary to
634 avoid surpassing the operating system limit on argument and environment
635 vector size. This is important when someone wants to diff or stat a
636 subdirectory, which requires Meta-CVS to pick out the individual files
637 at the CVS level.
639 The tag, log, status and annotate commands are now available.
641 The MAP file is sorted on F- file names now, not path names. This
642 improves merging, since files do not move within the file when
643 they are renamed.
645 Release 0.3, 2002-02-02:
647 Process termination done is properly in top level handler, by a nonlocal
648 exit. The program properly indicates failed termination when it exits
649 due to an error condition.
651 Corrections are made in the command line option processing. If z is an
652 option that takes an argument, and the argument is -zx, then x is
653 treated as the argument to the option. Long options arguments are
654 recognized properly, according to the --opt=arg convention. The option
655 processing is restructured. Most of the commands now take the
656 appropriate cvs command-specific options.
658 The update algorithm performs dupe checking over the map, which could
659 happen during a merge.
661 Some more bugfixing has been done to the move command. It was still not
662 handling right some cases of an unversioned file being clobbered. Also,
663 it wasn't renaming a directory containing just one file.
665 I did some performance investigation for larger file sets, and
666 ended up rewriting the code that computes filesystem restructuring
667 changes and map duplicates.
669 Release 0.2, 2002-01-30:
671 Changed official name from MCVS to Meta-CVS. The move command now
672 performs some filesystem tests so it does the right thing when a versioned
673 file is moved over a non-versioned file, or when a file is moved into
674 a directory not known to Meta-CVS. Factored out reading and writing of
675 map files into functions.
677 Release 0.1, 2002-01-28:
679 Support for mcvs diff -u added. The -R option works for mcvs add command.
680 Bug fixed in mcvs mv command; it wasn't working analogously to the Unix
681 mv command when copying a directory to an existing directory.
683 Release 0.0, 2002-01-27:
685 This is alpha software. It is not complete, and lacks documentation.
686 However, it is already usable in its present state and is being used for
687 version control by its author. If you can program in Common Lisp and would
688 like to help, take a look through the TODO file. Send me patches, ideas,
689 feature requests.

  ViewVC Help
Powered by ViewVC 1.1.5