GNU bug report logs - #61712
30.0.50; Want way to generate VC log for arbitrary list of files

Previous Next

Full log

View this message in rfc822 format

From: Filipp Gunbin <fgunbin <at> fastmail.fm>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: spwhitton <at> spwhitton.name, 61712 <at> debbugs.gnu.org, Juri Linkov <juri <at> 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

On 23/02/2023 20:12 +0200, Eli Zaretskii wrote:

>> From: Juri Linkov <juri <at> linkov.net>
>> Cc: Sean Whitton <spwhitton <at> spwhitton.name>,  61712 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.