* doc/emacs/vc1-xtra.texi (Revision Tags): Add a cross reference.

This commit is contained in:
Xue Fuqiao 2013-06-09 17:20:49 +08:00
parent 04fcf1b047
commit 2bc4a7255d
2 changed files with 26 additions and 15 deletions

View file

@ -1,3 +1,7 @@
2013-06-09 Xue Fuqiao <xfq.free@gmail.com>
* vc1-xtra.texi (Revision Tags): Add a cross reference.
2013-06-07 Xue Fuqiao <xfq.free@gmail.com> 2013-06-07 Xue Fuqiao <xfq.free@gmail.com>
* maintaining.texi (Branches): Remove text copied from other * maintaining.texi (Branches): Remove text copied from other

View file

@ -199,21 +199,28 @@ through VC@. Most later systems (including CVS, Subversion, bzr, git,
and hg) have a native tag facility, and VC uses it where available; and hg) have a native tag facility, and VC uses it where available;
those tags will be visible even when you bypass VC. those tags will be visible even when you bypass VC.
In a file-oriented VCS, when you rename a registered file you need In file-based version control systems, when you rename a registered
to rename its master along with it; the command @code{vc-rename-file} file you need to rename its master along with it; the command
will do this automatically. If you are using SCCS, you must also @code{vc-rename-file} will do this automatically
update the records of the tag, to mention the file by its new name @iftex
(@code{vc-rename-file} does this, too). An old tag that refers to a (@pxref{VC Delete/Rename,,,emacs, the Emacs Manual}).
master file that no longer exists under the recorded name is invalid; @end iftex
VC can no longer retrieve it. It would be beyond the scope of this @ifnottex
manual to explain enough about RCS and SCCS to explain how to update (@pxref{VC Delete/Rename}).
the tags by hand. Using @code{vc-rename-file} makes the tag remain @end ifnottex
valid for retrieval, but it does not solve all problems. For example, If you are using SCCS, you must also update the records of the tag, to
some of the files in your program probably refer to others by name. mention the file by its new name (@code{vc-rename-file} does this,
At the very least, the makefile probably mentions the file that you too). An old tag that refers to a master file that no longer exists
renamed. If you retrieve an old tag, the renamed file is retrieved under the recorded name is invalid; VC can no longer retrieve it. It
under its new name, which is not the name that the makefile expects. would be beyond the scope of this manual to explain enough about RCS
So the program won't really work as retrieved. and SCCS to explain how to update the tags by hand. Using
@code{vc-rename-file} makes the tag remain valid for retrieval, but it
does not solve all problems. For example, some of the files in your
program probably refer to others by name. At the very least, the
makefile probably mentions the file that you renamed. If you retrieve
an old tag, the renamed file is retrieved under its new name, which is
not the name that the makefile expects. So the program won't really
work as retrieved.
@node Version Headers @node Version Headers
@subsubsection Inserting Version Control Headers @subsubsection Inserting Version Control Headers