/contrib/cvs/ChangeLog.zoo

https://bitbucket.org/freebsd/freebsd-head/ · Unknown · 700 lines · 526 code · 174 blank · 0 comment · 0 complexity · 35acfd312b21601e6e23719a687d69a0 MD5 · raw file

  1. Thu Sep 15 14:19:21 1994 david d `zoo' zuhn <zoo@monad.armadillo.com>
  2. * Makefile.in: define TEXI2DVI, add it to FLAGS_TO_PASS; remove
  3. old comments about parameters for DEFS
  4. Wed Jul 13 21:54:46 1994 david d `zoo' zuhn (zoo@monad.armadillo.com)
  5. * contrib/rcs-to-cvs: rewritten for Bourne shell (thanks to David
  6. MacKenzie <djm@cygnus.com>)
  7. Wed Jul 13 21:48:38 1994 Ken Raeburn (raeburn@cujo.cygnus.com)
  8. * Makefile.in: Deleted line consisting of only whitespace; it
  9. confuses some versions of make.
  10. Mon Jan 24 12:26:47 1994 david d zuhn (zoo@monad.armadillo.com)
  11. * configure.in: check for <sys/select.h> and <ndbm.h>
  12. * Makefile.in: define YACC and not BISON
  13. Sat Dec 18 00:52:04 1993 david d zuhn (zoo@monad.armadillo.com)
  14. * config.h.in: handle HAVE_SYS_WAIT_H, HAVE_ERRNO_H
  15. * configure.in: check for memmove, <errno.h>
  16. * Makefile.in (VPATH): don't use $(srcdir), but @srcdir@ instead
  17. * configure.in (AC_HAVE_HEADERS): check for <sys/wait.h>
  18. Mon Nov 29 15:05:43 1993 K. Richard Pixley (rich@sendai.cygnus.com)
  19. * lib/Makefile.in, src/Makefile.in (CFLAGS): default to -g.
  20. * src/log.c (log_fileproc): if a file has been added, but not
  21. committed, then say so rather than reporting that nothing is
  22. known.
  23. * src/sanity.el: update for emacs-19.
  24. * src/RCS-patches, src/README-rm-add: update for rcs-5.6.6.
  25. * src/Makefile.in: removed some gratuitous diffs from cvs-1.3.
  26. * src/cvsrc.c: strdup -> xstrdup, malloc -> xmalloc, comment about
  27. fgets lossage.
  28. * configure, configure.in, Makefile.in: support man and doc
  29. directories and info and dvi targets.
  30. * doc/cvs.texinfo: comment out include of gpl.texinfo.
  31. * doc/Makefile.in: added dvi & info targets.
  32. * doc/cvsclient.texi: added @setfilename.
  33. * lib/Makefile.in: remove some extraneous diffs against the
  34. patched cvs-1.3.
  35. * doc/Makefile.in, man/Makefile.in: update for autoconf.
  36. Fri Nov 19 12:56:34 1993 K. Richard Pixley (rich@sendai.cygnus.com)
  37. * Many files: added configure.in, updated configure based on
  38. autoconf.
  39. Tue Jun 1 17:02:41 1993 david d `zoo' zuhn (zoo at cirdan.cygnus.com)
  40. * configure: add support for alloca and sys/select.h
  41. Wed May 19 19:34:48 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
  42. * cvs-format.el: Don't set c-tab-always-indent.
  43. Mon Mar 22 23:25:33 1993 david d `zoo' zuhn (zoo at cirdan.cygnus.com)
  44. * Makefile.in: installcheck: recurse into src directory to run tests
  45. Mon Jan 18 17:21:16 1993 K. Richard Pixley (rich@rtl.cygnus.com)
  46. * Makefile.in (check): recur into src directory in order to pick
  47. up the sanity check.
  48. Thu Dec 17 19:41:22 1992 david d `zoo' zuhn (zoo at cirdan.cygnus.com)
  49. * Makefile.in: added blank 'dvi' target
  50. Tue Apr 7 15:55:25 1992 Brian Berliner (berliner at sun.com)
  51. * Changes between CVS 1.3 Beta-3 and official CVS 1.3!
  52. * A new shell script is provided, "./cvsinit", which can be run at
  53. install time to help setup your $CVSROOT area. This can greatly
  54. ease your entry into CVS usage.
  55. * The INSTALL file has been updated to include the machines on
  56. which CVS has compiled successfully. I think CVS 1.3 is finally
  57. portable. Thanks to all the Beta testers!
  58. * Support for the "editinfo" file was contributed. This file
  59. (located in $CVSROOT/CVSROOT) can be used to specify a special
  60. "editor" to run on a per-directory basis within the repository,
  61. instead of the usual user's editor. As such, it can verify that
  62. the log message entered by the user is of the appropriate form
  63. (contains a bugid and test validation, for example).
  64. * The manual pages cvs(1) and cvs(5) have been updated.
  65. * The "mkmodules" command now informs you when your modules file
  66. has duplicate entries.
  67. * The "add" command now preserves any per-directory sticky tag when
  68. you add a new directory to your checked-out sources.
  69. * The "admin" command is now a fully recursive interface to the
  70. "rcs" program which operates on your checked-out sources. It no
  71. longer requires you to specify the full path to the RCS file.
  72. * The per-file sticky tags can now be effectively removed with
  73. "cvs update -A file", even if you had checked out the whole
  74. directory with a per-directory sticky tag. This allows a great
  75. deal of flexibility in managing the revisions that your checked-out
  76. sources are based upon (both per-directory and per-file sticky
  77. tags).
  78. * The "cvs -n commit" command now works, to show which files are
  79. out-of-date and will cause the real commit to fail, or which files
  80. will fail any pre-commit checks. Also, the "cvs -n import ..."
  81. command will now show you what it would've done without actually
  82. doing it.
  83. * Doing "cvs commit modules" to checkin the modules file will no
  84. properly run the "mkmodules" program (assuming you have setup your
  85. $CVSROOT/CVSROOT/modules file to do so).
  86. * The -t option in the modules file (which specifies a program to
  87. run when you do a "cvs rtag" operation on a module) now gets the
  88. symbolic tag as the second argument when invoked.
  89. * When the source repository is locked by another user, that user's
  90. login name will be displayed as the holder of the lock.
  91. * Doing "cvs checkout module/file.c" now works even if
  92. module/file.c is in the Attic (has been removed from main-line
  93. development).
  94. * Doing "cvs commit */Makefile" now works as one would expect.
  95. Rather than trying to commit everything recursively, it will now
  96. commit just the files specified.
  97. * The "cvs remove" command is now fully recursive. To schedule a
  98. file for removal, all you have to do is "rm file" and "cvs rm".
  99. With no arguments, "cvs rm" will schedule all files that have been
  100. physically removed for removal from the source repository at the
  101. next "cvs commit".
  102. * The "cvs tag" command now prints "T file" for each file that was
  103. tagged by this invocation and "D file" for each file that had the
  104. tag removed (as with "cvs tag -d").
  105. * The -a option has been added to "cvs rtag" to force it to clean
  106. up any old, matching tags for files that have been removed (in the
  107. Attic) that may not have been touched by this tag operation. This
  108. can help keep a consistent view with your tag, even if you re-use
  109. it frequently.
  110. Sat Feb 29 16:02:05 1992 Brian Berliner (berliner at sun.com)
  111. * Changes between CVS 1.3 Beta-2 and CVS 1.3 Beta-3
  112. * Many portability fixes, thanks to all the Beta testers! With any
  113. luck, this Beta release will compile correctly on most anything.
  114. Hey, what are we without our dreams.
  115. * CVS finally has support for doing isolated development on a
  116. branch off the current (or previous!) revisions. This is also
  117. extremely nice for generating patches for previously released
  118. software while development is progressing on the next release.
  119. Here's an example of creating a branch to fix a patch with the 2.0
  120. version of the "foo" module, even though we are already well into
  121. the 3.0 release. Do:
  122. % cvs rtag -b -rFOO_2_0 FOO_2_0_Patch foo
  123. % cvs checkout -rFOO_2_0_Patch foo
  124. % cd foo
  125. [[ hack away ]]
  126. % cvs commit
  127. A physical branch will be created in the RCS file only when you
  128. actually commit the change. As such, forking development at some
  129. random point in time is extremely light-weight -- requiring just a
  130. symbolic tag in each file until a commit is done. To fork
  131. development at the currently checked out sources, do:
  132. % cvs tag -b Personal_Hack
  133. % cvs update -rPersonal_Hack
  134. [[ hack away ]]
  135. % cvs commit
  136. Now, if you decide you want the changes made in the Personal_Hack
  137. branch to be merged in with other changes made in the main-line
  138. development, you could do:
  139. % cvs commit # to make Personal_Hack complete
  140. % cvs update -A # to update sources to main-line
  141. % cvs update -jPersonal_Hack # to merge Personal_Hack
  142. to update your checked-out sources, or:
  143. % cvs checkout -jPersonal_Hack module
  144. to checkout a fresh copy.
  145. To support this notion of forked development, CVS reserves
  146. all even-numbered branches for its own use. In addition, CVS
  147. reserves the ".0" and ".1" branches. So, if you intend to do your
  148. own branches by hand with RCS, you should use odd-numbered branches
  149. starting with ".3", as in "1.1.3", "1.1.5", 1.2.9", ....
  150. * The "cvs commit" command now supports a fully functional -r
  151. option, allowing you to commit your changes to a specific numeric
  152. revision or symbolic tag with full consistency checks. Numeric
  153. tags are useful for bringing your sources all up to some revision
  154. level:
  155. % cvs commit -r2.0
  156. For symbolic tags, you can only commit to a tag that references a
  157. branch in the RCS file. One created by "cvs rtag -b" or from
  158. "cvs tag -b" is appropriate (see below).
  159. * Roland Pesch <pesch@cygnus.com> and K. Richard Pixley
  160. <rich@cygnus.com> were kind enough to contribute two new manual
  161. pages for CVS: cvs(1) and cvs(5). Most of the new CVS 1.3 features
  162. are now documented, with the exception of the new branch support
  163. added to commit/rtag/tag/checkout/update.
  164. * The -j options of checkout/update have been added. The "cvs join"
  165. command has been removed.
  166. With one -j option, CVS will merge the changes made between the
  167. resulting revision and the revision that it is based on (e.g., if
  168. the tag refers to a branch, CVS will merge all changes made in
  169. that branch into your working file).
  170. With two -j options, CVS will merge in the changes between the two
  171. respective revisions. This can be used to "remove" a certain delta
  172. from your working file. E.g., If the file foo.c is based on
  173. revision 1.6 and I want to remove the changes made between 1.3 and
  174. 1.5, I might do:
  175. % cvs update -j1.5 -j1.3 foo.c # note the order...
  176. In addition, each -j option can contain on optional date
  177. specification which, when used with branches, can limit the chosen
  178. revision to one within a specific date. An optional date is
  179. specified by adding a colon (:) to the tag, as in:
  180. -jSymbolic_Tag:Date_Specifier
  181. An example might be what "cvs import" tells you to do when you have
  182. just imported sources that have conflicts with local changes:
  183. % cvs checkout -jTAG:yesterday -jTAG module
  184. which tells CVS to merge in the changes made to the branch
  185. specified by TAG in the last 24 hours. If this is not what is
  186. intended, substitute "yesterday" for whatever format of date that
  187. is appropriate, like:
  188. % cvs checkout -jTAG:'1 week ago' -jTAG module
  189. * "cvs diff" now supports the special tags "BASE" and "HEAD". So,
  190. the command:
  191. % cvs diff -u -rBASE -rHEAD
  192. will effectively show the changes made by others (in unidiff
  193. format) that will be merged into your working sources with your
  194. next "cvs update" command. "-rBASE" resolves to the revision that
  195. your working file is based on. "-rHEAD" resolves to the current
  196. head of the branch or trunk that you are working on.
  197. * The -P option of "cvs checkout" now means to Prune empty
  198. directories, as with "update". The default is to not remove empty
  199. directories. However, if you do "checkout" with any -r options, -P
  200. will be implied. I.e., checking out with a tag will cause empty
  201. directories to be pruned automatically.
  202. * The new file INSTALL describes how to install CVS, including
  203. detailed descriptions of interfaces to "configure".
  204. * The example loginfo file in examples/loginfo has been updated to
  205. use the perl script included in contrib/log.pl. The nice thing
  206. about this log program is that it records the revision numbers of
  207. your change in the log message.
  208. Example files for commitinfo and rcsinfo are now included in the
  209. examples directory.
  210. * All "#if defined(__STDC__) && __STDC__ == 1" lines have been
  211. changed to be "#if __STDC__" to fix some problems with the former.
  212. * The lib/regex.[ch] files have been updated to the 1.3 release of
  213. the GNU regex package.
  214. * The ndbm emulation routines included with CVS 1.3 Beta-2 in the
  215. src/ndbm.[ch] files has been moved into the src/myndbm.[ch] files
  216. to avoid any conflict with the system <ndbm.h> header file. If
  217. you had a previous CVS 1.3 Beta release, you will want to "cvs
  218. remove ndbm.[ch]" form your copy of CVS as well.
  219. * "cvs add" and "cvs remove" are a bit more verbose, telling you
  220. what to do to add/remove your file permanently.
  221. * We no longer mess with /dev/tty in "commit" and "add".
  222. * More things are quiet with the -Q option set.
  223. * New src/config.h option: If CVS_BADROOT is set, CVS will not
  224. allow people really logged in as "root" to commit changes.
  225. * "cvs diff" exits with a status of 0 if there were no diffs, 1 if
  226. there were diffs, and 2 if there were errors.
  227. * "cvs -n diff" is now supported so that you can still run diffs
  228. even while in the middle of committing files.
  229. * Handling of the CVS/Entries file is now much more robust.
  230. * The default file ignore list now includes "*.so".
  231. * "cvs import" did not expand '@' in the log message correctly. It
  232. does now. Also, import now uses the ignore file facility
  233. correctly.
  234. Import will now tell you whether there were conflicts that need to
  235. be resolved, and how to resolve them.
  236. * "cvs log" has been changed so that you can "log" things that are
  237. not a part of the current release (in the Attic).
  238. * If you don't change the editor message on commit, CVS now prompts
  239. you with the choice:
  240. !)reuse this message unchanged for remaining dirs
  241. which allows you to tell CVS that you have no intention of changing
  242. the log message for the remainder of the commit.
  243. * It is no longer necessary to have CVSROOT set if you are using
  244. the -H option to get Usage information on the commands.
  245. * Command argument changes:
  246. checkout: -P handling changed as described above.
  247. New -j option (up to 2 can be specified)
  248. for doing rcsmerge kind of things on
  249. checkout.
  250. commit: -r option now supports committing to a
  251. numeric or symbolic tags, with some
  252. restrictions. Full consistency checks will
  253. be done.
  254. Added "-f logfile" option, which tells
  255. commit to glean the log message from the
  256. specified file, rather than invoking the
  257. editor.
  258. rtag: Added -b option to create a branch tag,
  259. useful for creating a patch for a previous
  260. release, or for forking development.
  261. tag: Added -b option to create a branch tag,
  262. useful for creating a patch for a previous
  263. release, or for forking development.
  264. update: New -j option (up to 2 can be specified)
  265. for doing rcsmerge kind of things on
  266. update.
  267. Thu Jan 9 10:51:35 MST 1992 Jeff Polk (polk at BSDI.COM)
  268. * Changes between CVS 1.3 Beta-1 and CVS 1.3 Beta-2
  269. * Thanks to K. Richard Pixley at Cygnus we now have function
  270. prototypes in all the files
  271. * Some small changes to configure for portability. There have
  272. been other portability problems submitted that have not been fixed
  273. (Brian will be working on those). Additionally all __STDC__
  274. tests have been modified to check __STDC__ against the constant 1
  275. (this is what the Second edition of K&R says must be true).
  276. * Lots of additional error checking for forked processes (run_exec)
  277. (thanks again to K. Richard Pixley)
  278. * Lots of miscellaneous bug fixes - including but certainly not
  279. limited to:
  280. various commit core dumps
  281. various update core dumps
  282. bogus results from status with numeric sticky tags
  283. commitprog used freed memory
  284. Entries file corruption caused by No_Difference
  285. commit to revision broken (now works if branch exists)
  286. ignore file processing broken for * and !
  287. ignore processing didn't handle memory reasonably
  288. miscellaneous bugs in the recursion processor
  289. file descriptor leak in ParseInfo
  290. CVSROOT.adm->CVSROOT rename bug
  291. lots of lint fixes
  292. * Reformatted all the code in src (with GNU indent) and then
  293. went back and fixed prototypes, etc since indent gets confused. The
  294. rationale is that it is better to do it sooner than later and now
  295. everything is consistent and will hopefully stay that way.
  296. The basic options to indent were: "-bad -bbb -bap -cdb -d0 -bl -bli0
  297. -nce -pcs -cs -cli4 -di1 -nbc -psl -lp -i4 -ip4 -c41" and then
  298. miscellaneous formatting fixes were applied. Note also that the
  299. "-nfc1" or "-nfca" may be appropriate in files where comments have
  300. been carefully formatted (e.g, modules.c).
  301. Sat Dec 14 20:35:22 1991 Brian Berliner (berliner at sun.com)
  302. * Changes between CVS 1.2 and CVS 1.3 Beta are described here.
  303. * Lots of portability work. CVS now uses the GNU "configure"
  304. script to dynamically determine the features provided by your
  305. system. It probably is not foolproof, but it is better than
  306. nothing. Please let me know of any portability problems. Some
  307. file names were changed to fit within 14-characters.
  308. * CVS has a new RCS parser that is much more flexible and
  309. extensible. It should read all known RCS ",v" format files.
  310. * Most of the commands now are fully recursive, rather than just
  311. operating on the current directory alone. This includes "commit",
  312. which makes it real easy to do an "atomic" commit of all the
  313. changes made to a CVS hierarchy of sources. Most of the commands
  314. also correctly handle file names that are in directories other than
  315. ".", including absolute path names. Commands now accept the "-R"
  316. option to force recursion on (though it is always the default now)
  317. and the "-l" option to force recursion off, doing just "." and not
  318. any sub-directories.
  319. * CVS supports many of the features provided with the RCS 5.x
  320. distribution - including the new "-k" keyword expansion options. I
  321. recommend using RCS 5.x (5.6 is the current official RCS version)
  322. and GNU diff 1.15 (or later) distributions with CVS.
  323. * Checking out files with symbolic tags/dates is now "sticky", in
  324. that CVS remembers the tag/date used for each file (and directory)
  325. and will use that tag/date automatically on the next "update" call.
  326. This stickyness also holds for files checked out with the the new
  327. RCS 5.x "-k" options.
  328. * The "cvs diff" command now recognizes all of the rcsdiff 5.x
  329. options. Unidiff format is available by installing the GNU
  330. diff 1.15 distribution.
  331. * The old "CVS.adm" directories created on checkout are now called
  332. "CVS" directories, to look more like "RCS" and "SCCS". Old CVS.adm
  333. directories are automagically converted to CVS directories. The
  334. old "CVSROOT.adm" directory within the source repository is
  335. automagically changed into a "CVSROOT" directory as well.
  336. * Symbolic links in the source repository are fully supported ONLY
  337. if you use RCS 5.6 or later and (of course) your system supports
  338. symlinks.
  339. * A history database has been contributed which maintains the
  340. history of certain CVS operations, as well as providing a wide array
  341. of querying options.
  342. * The "cvs" program has a "-n" option which can be used with the
  343. "update" command to show what would be updated without actually
  344. doing the update, like: "cvs -n update". All usage statements
  345. have been cleaned up and made more verbose.
  346. * The module database parsing has been rewritten. The new format
  347. is compatible with the old format, but with much more
  348. functionality. It allows modules to be created that grab pieces or
  349. whole directories from various different parts of your source
  350. repository. Module-relative specifications are also correctly
  351. recognized now, like "cvs checkout module/file.c".
  352. * A configurable template can be specified such that on a "commit",
  353. certain directories can supply a template that the user must fill
  354. before completing the commit operation.
  355. * A configurable pre-commit checking program can be specified which
  356. will run to verify that a "commit" can happen. This feature can be
  357. used to restrict certain users from changing certain pieces of the
  358. source repository, or denying commits to the entire source
  359. repository.
  360. * The new "cvs export" command is much like "checkout", but
  361. establishes defaults suitable for exporting code to others (expands
  362. out keywords, forces the use of a symbolic tag, and does not create
  363. "CVS" directories within the checked out sources.
  364. * The new "cvs import" command replaces the deprecated "checkin"
  365. shell script and is used to import sources into CVS control. It is
  366. also much faster for the first-time import. Some algorithmic
  367. improvements have also been made to reduce the number of
  368. conflicting files on next-time imports.
  369. * The new "cvs admin" command is basically an interface to the
  370. "rcs" program. (Not yet implemented very well).
  371. * Signal handling (on systems with BSD or POSIX signals) is much
  372. improved. Interrupting CVS now works with a single interrupt!
  373. * CVS now invokes RCS commands by direct fork/exec rather than
  374. calling system(3). This improves performance by removing a call to
  375. the shell to parse the arguments.
  376. * Support for the .cvsignore file has been contributed. CVS will
  377. now show "unknown" files as "? filename" as the result of an "update"
  378. command. The .cvsignore file can be used to add files to the
  379. current list of ignored files so that they won't show up as unknown.
  380. * Command argument changes:
  381. cvs: Added -l to turn off history logging.
  382. Added -n to show what would be done without actually
  383. doing anything.
  384. Added -q/-Q for quiet and really quiet settings.
  385. Added -t to show debugging trace.
  386. add: Added -k to allow RCS 5.x -k options to be specified.
  387. admin: New command; an interface to rcs(1).
  388. checkout: Added -A to reset sticky tags/date/options.
  389. Added -N to not shorten module paths.
  390. Added -R option to force recursion.
  391. Changed -p (prune empty directories) to -P option.
  392. Changed -f option; forcing tags match is now default.
  393. Added -p option to checkout module to standard output.
  394. Added -s option to cat the modules db with status.
  395. Added -d option to checkout in the specified directory.
  396. Added -k option to use RCS 5.x -k support.
  397. commit: Removed -a option; use -l instead.
  398. Removed -f option.
  399. Added -l option to disable recursion.
  400. Added -R option to force recursion.
  401. If no files specified, commit is recursive.
  402. diff: Now recognizes all RCS 5.x rcsdiff options.
  403. Added -l option to disable recursion.
  404. Added -R option to force recursion.
  405. history: New command; displays info about CVS usage.
  406. import: Replaces "checkin" shell script; imports sources
  407. under CVS control. Ignores files on the ignore
  408. list (see -I option or .cvsignore description above).
  409. export: New command; like "checkout", but w/special options
  410. turned on by default to facilitate exporting sources.
  411. join: Added -B option to join from base of the branch;
  412. join now defaults to only joining with the top two
  413. revisions on the branch.
  414. Added -k option for RCS 5.x -k support.
  415. log: Supports all RCS 5.x options.
  416. Added -l option to disable recursion.
  417. Added -R option to force recursion.
  418. patch: Changed -f option; forcing tags match is now default.
  419. Added -c option to force context-style diffs.
  420. Added -u option to support unidiff-style diffs.
  421. Added -V option to support RCS specific-version
  422. keyword expansion formats.
  423. Added -R option to force recursion.
  424. remove: No option changes. It's a bit more verbose.
  425. rtag: Equivalent to the old "cvs tag" command.
  426. No option changes. It's a lot faster for re-tag.
  427. status: New output formats with more information.
  428. Added -l option to disable recursion.
  429. Added -R option to force recursion.
  430. Added -v option to show symbolic tags for files.
  431. tag: Functionality changed to tag checked out files
  432. rather than modules; use "rtag" command to get the
  433. old "cvs tag" behaviour.
  434. update: Added -A to reset sticky tags/date/options.
  435. Changed -p (prune empty directories) to -P option.
  436. Changed -f option; forcing tags match is now default.
  437. Added -p option to checkout module to standard output.
  438. Added -I option to add files to the ignore list.
  439. Added -R option to force recursion.
  440. Major Contributors:
  441. * Jeff Polk <polk@bsdi.com> rewrote most of the grody code of CVS
  442. 1.2. He made just about everything dynamic (by using malloc),
  443. added a generic hashed list manager, re-wrote the modules database
  444. parsing in a compatible - but extended way, generalized directory
  445. hierarchy recursion for virtually all the commands (including
  446. commit!), generalized the loginfo file to be used for pre-commit
  447. checks and commit templates, wrote a new and flexible RCS parser,
  448. fixed an uncountable number of bugs, and helped in the design of
  449. future CVS features. If there's anything gross left in CVS, it's
  450. probably my fault!
  451. * David G. Grubbs <dgg@ksr.com> contributed the CVS "history" and
  452. "release" commands. As well as the ever-so-useful "-n" option of
  453. CVS which tells CVS to show what it would do, without actually
  454. doing it. He also contributed support for the .cvsignore file.
  455. * Paul Sander, HaL Computer Systems, Inc. <paul@hal.com> wrote and
  456. contributed the code in lib/sighandle.c. I added support for
  457. POSIX, BSD, and non-POSIX/non-BSD systems.
  458. * Free Software Foundation contributed the "configure" script and
  459. other compatibility support in the "lib" directory, which will help
  460. make CVS much more portable.
  461. * Many others have contributed bug reports and enhancement requests.
  462. Some have even submitted actual code which I have not had time yet
  463. to integrate into CVS. Maybe for the next release.
  464. * Thanks to you all!
  465. Wed Feb 6 10:10:58 1991 Brian Berliner (berliner at sun.com)
  466. * Changes from CVS 1.0 Patchlevel 1 to CVS 1.0 Patchlevel 2; also
  467. known as "Changes from CVS 1.1 to CVS 1.2".
  468. * Major new support with this release is the ability to use the
  469. recently-posted RCS 5.5 distribution with CVS 1.2. See below for
  470. other assorted bug-fixes that have been thrown in.
  471. * ChangeLog (new): Added Emacs-style change-log file to CVS 1.2
  472. release. Chronological description of changes between release.
  473. * README: Small fixes to installation instructions. My email
  474. address is now "berliner@sun.com".
  475. * src/Makefile: Removed "rcstime.h". Removed "depend" rule.
  476. * src/partime.c: Updated to RCS 5.5 version with hooks for CVS.
  477. * src/maketime.c: Updated to RCS 5.5 version with hooks for CVS.
  478. * src/rcstime.h: Removed from the CVS 1.2 distribution.
  479. Thanks to Paul Eggert <eggert@twinsun.com> for these changes.
  480. * src/checkin.csh: Support for RCS 5.5 parsing.
  481. Thanks to Paul Eggert <eggert@twinsun.com> for this change.
  482. * src/collect_sets.c (Collect_Sets): Be quieter if "-f" option is
  483. specified. When checking out files on-top-of other files that CVS
  484. doesn't know about, run a diff in the hopes that they are really
  485. the same file before aborting.
  486. * src/commit.c (branch_number): Fix for RCS 5.5 parsing.
  487. Thanks to Paul Eggert <eggert@twinsun.com> for this change.
  488. * src/commit.c (do_editor): Bug fix - fprintf missing argument
  489. which sometimes caused core dumps.
  490. * src/modules.c (process_module): Properly NULL-terminate
  491. update_dir[] in all cases.
  492. * src/no_difference.c (No_Difference): The wrong RCS revision was
  493. being registered in certain (strange) cases.
  494. * src/patch.c (get_rcsdate): New algorithm. No need to call
  495. maketime() any longer.
  496. Thanks to Paul Eggert <eggert@twinsun.com> for this change.
  497. * src/patchlevel.h: Increased patch level to "2".
  498. * src/subr.c (isdir, islink): Changed to compare stat mode bits
  499. correctly.
  500. * src/tag.c (tag_file): Added support for following symbolic links
  501. that are in the master source repository when tagging. Made tag
  502. somewhat quieter in certain cases.
  503. * src/update.c (update_process_lists): Unlink the user's file if it
  504. was put on the Wlist, meaning that the user's file is not modified
  505. and its RCS file has been removed by someone else.
  506. * src/update.c (update): Support for "cvs update dir" to correctly
  507. just update the argument directory "dir".
  508. * src/cvs.h: Fixes for RCS 5.5 parsing.
  509. * src/version_number.c (Version_Number): Fixes for parsing RCS 5.5
  510. and older RCS-format files.
  511. Thanks to Paul Eggert <eggert@twinsun.com> for these changes.
  512. * src/version_number.c (Version_Number): Bug fixes for "-f" option.
  513. Bug fixes for parsing with certain branch numbers. RCS
  514. revision/symbol parsing is much more solid now.
  515. Wed Feb 14 10:01:33 1990 Brian Berliner (berliner at sun.com)
  516. * Changes from CVS 1.0 Patchlevel 0 to CVS 1.0 Patchlevel 1; also
  517. known as "Changes from CVS 1.0 to CVS 1.1".
  518. * src/patch.c (get_rcsdate): Portability fix. Replaced call to
  519. timelocal() with call to maketime().
  520. Mon Nov 19 23:15:11 1990 Brian Berliner (berliner at prisma.com)
  521. * Sent CVS 1.0 release to comp.sources.unix moderator and FSF.
  522. * Special thanks to Dick Grune <dick@cs.vu.nl> for his work on the
  523. 1986 version of CVS and making it available to the world. Dick's
  524. version is available on uunet.uu.net in the
  525. comp.sources.unix/volume6/cvs directory.
  526. @(#)ChangeLog 1.17 92/04/10