From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: spwhitton@spwhitton.name, 61712@debbugs.gnu.org,
Juri Linkov <juri@linkov.net>
Subject: bug#61712: 30.0.50; Want way to generate VC log for arbitrary list of files
Date: Thu, 23 Feb 2023 23:15:12 +0300 [thread overview]
Message-ID: <m2lekogmun.fsf@fastmail.fm> (raw)
In-Reply-To: <83cz60p7y7.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 Feb 2023 20:12:16 +0200")
On 23/02/2023 20:12 +0200, Eli Zaretskii wrote:
>> From: Juri Linkov <juri@linkov.net>
>> Cc: Sean Whitton <spwhitton@spwhitton.name>, 61712@debbugs.gnu.org
>> Date: Thu, 23 Feb 2023 19:59:05 +0200
>>
>> > How could you know, when this important feature was almost completely
>> > undocumented? Apart of a single NEWS entry, which is also quite
>> > misleading in what it does NOT say, there was no mention of this
>> > anywhere in our manuals, until now.
>>
>> Adding text for such a minor feature as using Dired for VC commands
>> to the top node "Version Control" makes it too long.
>
> It isn't a minor feature, IMO. It enables a lot of workflows that
> previously were hard or impossible. The first example is the question
> which started this discussion.
Oh yes, and it isn't (wasn't) easily discoverable. Thanks for adding
that to manual.
prev parent reply other threads:[~2023-02-23 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 17:25 bug#61712: 30.0.50; Want way to generate VC log for arbitrary list of files Sean Whitton
2023-02-22 19:07 ` Juri Linkov
2023-02-22 22:19 ` Sean Whitton
2023-02-23 13:00 ` Eli Zaretskii
2023-02-23 17:59 ` Juri Linkov
2023-02-23 18:12 ` Eli Zaretskii
2023-02-23 20:15 ` Filipp Gunbin [this message]
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=m2lekogmun.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=61712@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.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).