diff options
| author | André Spiegel | 2001-02-22 10:18:11 +0000 |
|---|---|---|
| committer | André Spiegel | 2001-02-22 10:18:11 +0000 |
| commit | 60a441a536c8b14dfe8ad822d2a2b8102bbba6a3 (patch) | |
| tree | 5c6c4c2a908bc5461eadee4ff2e495b8b009178e | |
| parent | 089d639f33dbe16832e82fc52629dd8fc360519d (diff) | |
| download | emacs-60a441a536c8b14dfe8ad822d2a2b8102bbba6a3.tar.gz emacs-60a441a536c8b14dfe8ad822d2a2b8102bbba6a3.zip | |
Some corrections to the VC news.
| -rw-r--r-- | etc/NEWS | 25 |
1 files changed, 11 insertions, 14 deletions
| @@ -1528,7 +1528,7 @@ easier to plug-in arbitrary version control backends. (See Lisp | |||
| 1528 | Changes for details on the new structure.) As a result, the mechanism | 1528 | Changes for details on the new structure.) As a result, the mechanism |
| 1529 | to enable and disable support for particular version systems has | 1529 | to enable and disable support for particular version systems has |
| 1530 | changed: everything is now controlled by the new variable | 1530 | changed: everything is now controlled by the new variable |
| 1531 | `vc-handled-backends'. Its value is a list of atoms that identify | 1531 | `vc-handled-backends'. Its value is a list of symbols that identify |
| 1532 | version systems; the default is '(RCS CVS SCCS). When finding a file, | 1532 | version systems; the default is '(RCS CVS SCCS). When finding a file, |
| 1533 | each of the backends in that list is tried in order to see whether the | 1533 | each of the backends in that list is tried in order to see whether the |
| 1534 | file is registered in that backend. | 1534 | file is registered in that backend. |
| @@ -1584,14 +1584,11 @@ should come first in `vc-handled-backends', and the ``more remote'' | |||
| 1584 | backend (CVS) should come later. (The default value of | 1584 | backend (CVS) should come later. (The default value of |
| 1585 | `vc-handled-backends' already has it that way.) | 1585 | `vc-handled-backends' already has it that way.) |
| 1586 | 1586 | ||
| 1587 | If you have a file registered in one backend already, you can register | 1587 | You can then commit changes to another backend (say, RCS), by typing |
| 1588 | it in a second one by using C-x v i (vc-register) again. | 1588 | C-u C-x v v RCS RET (i.e. vc-next-action now accepts a backend name as |
| 1589 | Alternatively, you can commit changes to another backend (say, RCS), | 1589 | a revision number). VC registers the file in the more local backend |
| 1590 | by typing C-u C-x v v RCS RET (i.e. vc-next-action now accepts a | 1590 | if that hasn't already happened, and commits to a branch based on the |
| 1591 | backend name as a revision number). When using the latter approach, | 1591 | current revision number from the more remote backend. |
| 1592 | VC registers the file in the more local backend if that hasn't already | ||
| 1593 | happened, and commits to a branch based on the current revision number | ||
| 1594 | from the more remote backend. | ||
| 1595 | 1592 | ||
| 1596 | If a file is registered in multiple backends, you can switch to | 1593 | If a file is registered in multiple backends, you can switch to |
| 1597 | another one using C-x v b (vc-switch-backend). This does not change | 1594 | another one using C-x v b (vc-switch-backend). This does not change |
| @@ -1640,7 +1637,7 @@ is only meaningful if the CVSREAD variable is set, or if files are | |||
| 1640 | 1637 | ||
| 1641 | The commands C-x v s (vc-create-snapshot) and C-x v r | 1638 | The commands C-x v s (vc-create-snapshot) and C-x v r |
| 1642 | (vc-retrieve-snapshot) are now also implemented for CVS. If you give | 1639 | (vc-retrieve-snapshot) are now also implemented for CVS. If you give |
| 1643 | an empty argument to the latter, that performs a `cvs update', | 1640 | an empty snapshot name to the latter, that performs a `cvs update', |
| 1644 | starting at the given directory. | 1641 | starting at the given directory. |
| 1645 | 1642 | ||
| 1646 | *** Lisp Changes in VC | 1643 | *** Lisp Changes in VC |
| @@ -1649,11 +1646,11 @@ VC has been restructured internally to make it modular. You can now | |||
| 1649 | add support for arbitrary version control backends by writing a | 1646 | add support for arbitrary version control backends by writing a |
| 1650 | library that provides a certain set of backend-specific functions, and | 1647 | library that provides a certain set of backend-specific functions, and |
| 1651 | then telling VC to use that library. For example, to add support for | 1648 | then telling VC to use that library. For example, to add support for |
| 1652 | a version system named FOO, you write a library named vc-foo.el, which | 1649 | a version system named SYS, you write a library named vc-sys.el, which |
| 1653 | provides a number of functions vc-foo-... (see commentary at the end | 1650 | provides a number of functions vc-sys-... (see commentary at the top |
| 1654 | of vc.el for a detailed list of them). To make VC use that library, | 1651 | of vc.el for a detailed list of them). To make VC use that library, |
| 1655 | you need to put it somewhere into Emacs' load path and add the atom | 1652 | you need to put it somewhere into Emacs' load path and add the symbol |
| 1656 | `FOO' to the list `vc-handled-backends'. | 1653 | `SYS' to the list `vc-handled-backends'. |
| 1657 | 1654 | ||
| 1658 | *** The customizable EDT emulation package now supports the EDT | 1655 | *** The customizable EDT emulation package now supports the EDT |
| 1659 | SUBS command and EDT scroll margins. It also works with more | 1656 | SUBS command and EDT scroll margins. It also works with more |