From: "Richard M. Stallman" <rms@gnu.org>
Cc: Aaron.Hawley@uvm.edu, emacs-devel@gnu.org
Subject: Re: log-view documentation
Date: Wed, 23 Nov 2005 22:57:31 -0500 [thread overview]
Message-ID: <E1Ef8El-0007Tw-2n@fencepost.gnu.org> (raw)
In-Reply-To: <17284.9087.508309.641956@kahikatea.snap.net.nz> (message from Nick Roberts on Wed, 23 Nov 2005 21:08:31 +1300)
I would guess he has looked at other lists in the manual. The above style is
currently used for vc-annotate (Node: Old Versions).
If vc-annotate is inconsistent with the rest of the manual,
I think that needs to be fixed. We should clean up inconcistency
that serves no particular purpose, not extend it.
Here I have put that table into our usual format.
I have also tried clearing up certain descriptions
whose meaning I was not certain of. I am partly guessing
(since I don't use this feature), so if any of this is wrong,
could someone tell me?
@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 revision indicated the current line line
and the revision before it. This is useful to see what actually
changed when the revision indicated by the current line was committed.
@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
next prev parent reply other threads:[~2005-11-24 3:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 17:45 log-view documentation Aaron S. Hawley
2005-11-23 5:14 ` Richard M. Stallman
2005-11-23 8:08 ` Nick Roberts
2005-11-24 3:57 ` Richard M. Stallman [this message]
2005-11-24 6:06 ` Nick Roberts
2005-11-25 15:49 ` Richard M. Stallman
2005-11-25 21:59 ` Nick Roberts
2005-11-26 0:45 ` Aaron S. Hawley
2005-11-26 0:41 ` Aaron S. Hawley
2005-11-26 16:21 ` Richard M. Stallman
[not found] <E1EmOvm-0006dY-1f@fencepost.gnu.org>
2005-12-14 6:09 ` Aaron S. Hawley
2005-12-14 10:08 ` Juri Linkov
2005-12-14 18:45 ` Aaron S. Hawley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Ef8El-0007Tw-2n@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=Aaron.Hawley@uvm.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).