From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 58383@debbugs.gnu.org, spwhitton@spwhitton.name
Subject: bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately
Date: Sun, 13 Nov 2022 18:35:37 +0200 [thread overview]
Message-ID: <83bkpalsme.fsf@gnu.org> (raw)
In-Reply-To: <87a64vvtyh.fsf@posteo.net> (message from Philip Kaludercic on Sun, 13 Nov 2022 13:56:38 +0000)
> Cc: 58383@debbugs.gnu.org
> From: Philip Kaludercic <philipk@posteo.net>
> Date: Sun, 13 Nov 2022 13:56:38 +0000
>
> --- a/lisp/vc/vc.el
> +++ b/lisp/vc/vc.el
> @@ -3391,14 +3391,24 @@ vc-prepare-patch
> as the default subject for the message (and it will be prompted
> for when called interactively). Otherwise a separate message
> will be composed for each revision, with SUBJECT derived from the
> -invidividual commits.
> -
> -When invoked interactively in a Log View buffer with marked
> -revisions, those revisions will be used."
> +invidividual commits. When invoked with a numerical prefix
> +argument, the last N revisions will be used. When invoked
> +interactively in a Log View buffer with marked revisions, those
> +revisions will be used."
Can we take this opportunity to get rid of the passive voice and
clarify the doc string, please?
Thanks.
next prev parent reply other threads:[~2022-11-13 16:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 17:49 bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately Sean Whitton
2022-10-09 12:54 ` Philip Kaludercic
2022-11-04 22:21 ` Philip Kaludercic
2022-11-06 21:44 ` Sean Whitton
2022-11-06 21:49 ` Philip Kaludercic
2022-11-07 23:06 ` Sean Whitton
2022-11-08 20:31 ` Philip Kaludercic
2022-11-08 21:00 ` Sean Whitton
2022-11-09 8:28 ` Philip Kaludercic
2022-11-09 16:36 ` Sean Whitton
2022-11-09 17:46 ` Philip Kaludercic
2022-11-09 20:56 ` Sean Whitton
2022-11-10 20:14 ` Philip Kaludercic
2022-11-11 0:07 ` Sean Whitton
2022-11-11 6:32 ` Philip Kaludercic
2022-11-11 20:53 ` Sean Whitton
2022-11-13 13:56 ` Philip Kaludercic
2022-11-13 16:06 ` Philip Kaludercic
2022-11-13 16:35 ` Eli Zaretskii [this message]
2022-11-13 16:45 ` Philip Kaludercic
2022-11-13 16:52 ` Eli Zaretskii
2022-11-13 18:17 ` Philip Kaludercic
2022-11-14 12:41 ` Eli Zaretskii
2022-11-16 0:04 ` Sean Whitton
2022-11-16 7:50 ` Philip Kaludercic
2022-11-11 7:34 ` Eli Zaretskii
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=83bkpalsme.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58383@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=spwhitton@spwhitton.name \
/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).