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:52:11 +0200 [thread overview]
Message-ID: <837czylrus.fsf@gnu.org> (raw)
In-Reply-To: <87fsemvm55.fsf@posteo.net> (message from Philip Kaludercic on Sun, 13 Nov 2022 16:45:26 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: spwhitton@spwhitton.name, 58383@debbugs.gnu.org
> Date: Sun, 13 Nov 2022 16:45:26 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can we take this opportunity to get rid of the passive voice and
> > clarify the doc string, please?
>
> Done:
Thanks, and the same with package-vc-prepare-patch, please?
Btw, this kind of reformatting:
> -SUBJECT and REVISIONS are passed on to `vc-prepare-patch', which see.
> -PKG must be a package description.
> -Interactively, prompt for PKG, SUBJECT, and REVISIONS. However,
> -if the current buffer has marked commit log entries, REVISIONS
> -are the tags of the marked entries, see `log-view-get-marked'."
> +SUBJECT and REVISIONS are passed on to `vc-prepare-patch', which
> +see. PKG must be a package description. Interactively, prompt
> +for PKG, SUBJECT, and REVISIONS. 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."
is IMO for the worse: when the sentence starting with "Interactively"
begins a new line, it stands out, which helps users find the most
relevant parts faster.
next prev parent reply other threads:[~2022-11-13 16:52 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
2022-11-13 16:45 ` Philip Kaludercic
2022-11-13 16:52 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837czylrus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.