stretch factor greater than 1 means the color range spans more than a
year.
-From the annotate buffer, you can use the following keys to browse the
+ From the annotate buffer, you can use the following keys to browse the
annotations of past revisions, view diffs, or view log entries:
-@itemize @bullet
-
-@item
-Pressing @kbd{P} annotates the previous revision. It also takes a
-numeric prefix argument, so for example @kbd{C-u 10 P} would take you
-back 10 revisions.
-
-@item
-Pressing @kbd{N} annotates the next revision. It also takes a numeric
-prefix argument, so for example @kbd{C-u 10 N} would take you forward
-10 revisions.
-
-@item
-Pressing @kbd{J} annotates the revision at line (as denoted by the
-version number on the same line).
-
-@item
-Pressing @kbd{A} annotates the revision previous to line (as denoted
-by the version number on the same line). This is useful to see the
-state the file was in before the change on the current line was made.
-
-@item
-Pressing @kbd{D} shows the diff of the revision at line with its
-previous revision. This is useful to see what actually changed when
-the revision denoted on the current line was committed.
-
-@item
-Pressing @kbd{L} shows the log of the revision at line. This is
-useful to see the author's description of the changes that occurred
-when the revision denoted on the current line was committed.
-
-@item
-Pressing @kbd{W} annotates the workfile (most up to date) version. If
-you used @kbd{P} and @kbd{N} to browse to other revisions, use this
-key to return to the latest version.
-@end itemize
+@table @kbd
+@item P
+Annotate the previous revision, that is to say, the revision before
+the one currently annotated. A numeric prefix argument is a repeat
+count, so @kbd{C-u 10 P} would take you back 10 revisions.
+
+@item N
+Annotate the next revision---the one after the revision currently
+annotated. A numeric prefix argument is a repeat count.
+
+@item J
+Annotate the revision indicated by the current line.
+
+@item A
+Annotate the revision before the one indicated by the current line.
+This is useful to see the state the file was in before the change on
+the current line was made.
+
+@item D
+Display the diff between the current line's revision and the previous
+revision. This is useful to see what the current line's revision
+actually changed in the file.
+
+@item L
+Show the log of the current line's revision. This is useful to see
+the author's description of the changes in the revision on the current
+line.
+
+@item W
+Annotate the workfile version--the one you are editing. If you used
+@kbd{P} and @kbd{N} to browse to other revisions, use this key to
+return to the latest version.
+@end table
@node Secondary VC Commands
@subsection The Secondary Commands of VC
If locking is in use, @kbd{C-x v i} leaves the file unlocked and
read-only. Type @kbd{C-x v v} if you wish to start editing it. After
registering a file with CVS, you must subsequently commit the initial
-version by typing @kbd{C-x v v}.
+version by typing @kbd{C-x v v}. Until you do that, the version
+appears as @samp{@@@@} in the mode line.
@vindex vc-default-init-version
@cindex initial version number to register
snapshot thus modified may not completely work (@pxref{Snapshot
Caveats}).
+ Some backends do not provide an explicit rename operation to their
+repositories. After issuing @code{vc-rename-file}, use @kbd{C-x v v}
+on the original and renamed buffers and provide the necessary edit
+log.
+
You cannot use @code{vc-rename-file} on a file that is locked by
someone else.