aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPhilip Kaludercic2022-10-11 18:09:58 +0200
committerPhilip Kaludercic2022-10-14 18:07:52 +0200
commitff0fe620024b79a1cae4e31c2f4ed6f857b9db9e (patch)
tree5ec0f9d52cd353069d78f7ca1ebbf5b8206089f9
parentbe1afa047f74f3197e530b28971249593b12d177 (diff)
downloademacs-ff0fe620024b79a1cae4e31c2f4ed6f857b9db9e.tar.gz
emacs-ff0fe620024b79a1cae4e31c2f4ed6f857b9db9e.zip
Mention that vc-prepare-patch can interact with a log-view
; * doc/emacs/vc1-xtra.texi (Preparing Patches): Extend documentation.
-rw-r--r--doc/emacs/vc1-xtra.texi9
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/emacs/vc1-xtra.texi b/doc/emacs/vc1-xtra.texi
index 66d3f51c306..23d5f504322 100644
--- a/doc/emacs/vc1-xtra.texi
+++ b/doc/emacs/vc1-xtra.texi
@@ -291,8 +291,13 @@ When collaborating on projects it is common to send patches via email,
291to share changes. If you wish to do this using VC, you can use the 291to share changes. If you wish to do this using VC, you can use the
292@code{vc-prepare-patch} command. This will prompt you for the 292@code{vc-prepare-patch} command. This will prompt you for the
293revisions you wish to share, and which destination email address(es) 293revisions you wish to share, and which destination email address(es)
294to use. The command will then prepare those revisions using your 294to use. The revisions are separated using commas (or whatever was
295@abbr{MUA, Mail User Agent} for you to review and send. 295configured by @var{crm-separator}). The command will then prepare
296those revisions using your @abbr{MUA, Mail User Agent} for you to
297review and send.
298
299When invoked interactively in a Log View buffer with marked revisions,
300these revisions will be used.
296 301
297@vindex vc-prepare-patches-separately 302@vindex vc-prepare-patches-separately
298Depending on the value of the user option 303Depending on the value of the user option