From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@janestreet.com, 62940@debbugs.gnu.org, fgunbin@fastmail.fm
Subject: bug#62940: 29.0.60; vc: no easy way to get diff of all outgoing changes
Date: Fri, 11 Oct 2024 17:40:14 +0300 [thread overview]
Message-ID: <a9f122e2-28fb-4a0d-9659-fde90ab732f5@gutov.dev> (raw)
In-Reply-To: <86v7xzyxyz.fsf@gnu.org>
On 11/10/2024 09:07, Eli Zaretskii wrote:
>> +@code{vc-diff} with a prefix argument: @kbd{C-u C-x v =}. This prompts
>> +for two revision IDs (@pxref{VCS Concepts}), and displays a diff between
>> +those versions of the fileset. The first one has several default
>> +values: the revision before the last one when the fileset changed, and
>> +the last revision of the current branch's upstream.
>> +The second defaults to nil, which means the contents of
> ^^^^^^^^^^
> "Second" is ambiguous here (because of how the previous sentence
> ends), so I suggest to say "The second revision ID" instead to
> disambiguate it.
Okay, that works.
next prev parent reply other threads:[~2024-10-11 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 19:12 bug#62940: 29.0.60; vc: no easy way to get diff of all outgoing changes Spencer Baugh
2023-04-18 20:36 ` Filipp Gunbin
2023-04-18 20:43 ` Dmitry Gutov
2023-04-19 6:49 ` Juri Linkov
2023-08-14 19:42 ` Spencer Baugh
2023-08-16 7:48 ` Juri Linkov
2024-09-13 20:54 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 2:11 ` Dmitry Gutov
2024-09-14 7:12 ` Eli Zaretskii
2024-10-10 0:26 ` Dmitry Gutov
2024-10-10 5:27 ` Eli Zaretskii
2024-10-11 1:13 ` Dmitry Gutov
2024-10-11 6:07 ` Eli Zaretskii
2024-10-11 14:40 ` Dmitry Gutov [this message]
2024-10-11 1:34 ` Dmitry Gutov
2024-10-11 14:39 ` Dmitry Gutov
2024-10-11 15:10 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11 20:28 ` Dmitry Gutov
2024-10-11 22:38 ` Dmitry Gutov
2024-10-12 8:32 ` Eli Zaretskii
2023-04-18 21:59 ` Spencer Baugh
2023-04-21 18:36 ` sbaugh
2023-04-22 6:57 ` Eli Zaretskii
2023-04-22 13:00 ` sbaugh
2023-04-22 13:17 ` Eli Zaretskii
2023-04-22 18:33 ` Dmitry Gutov
2023-04-22 19:27 ` 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=a9f122e2-28fb-4a0d-9659-fde90ab732f5@gutov.dev \
--to=dmitry@gutov.dev \
--cc=62940@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=sbaugh@janestreet.com \
/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).