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: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Sean Whitton <spwhitton <at> spwhitton.name>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#61712: closed (30.0.50; Want way to generate VC log for
 arbitrary list of files)
Date: Wed, 22 Feb 2023 22:20:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 22 Feb 2023 15:19:39 -0700
with message-id <87cz619wck.fsf <at> melete.silentflame.com>
and subject line Re: bug#61712: 30.0.50; Want way to generate VC log for arbitrary list of files
has caused the debbugs.gnu.org bug report #61712,
regarding 30.0.50; Want way to generate VC log for arbitrary list of files
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
61712: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61712
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.0.50; Want way to generate VC log for arbitrary list of files
Date: Wed, 22 Feb 2023 10:25:46 -0700

Hello,

Yesterday I wanted to review changes to some documentation files in a
repository; roughly, `git log -- dgit.1 *.pod`.  I would have preferred
to have the result in a *vc-log* buffer, but I don't believe we have a
command to do this.  'C-x v !' can't do it.

If there were changes to each of the files, they would have appeared in
*vc-dir*, and I could have used the new vc-dir-mark-by-regexp, and then
vc-print-log would have done the right thing.

So, I wonder if we could have a way to insert up-to-date files into
*vc-dir*, so that they could be used to select an arbitrary VC fileset?

-- 
Sean Whitton

[Message part 3 (message/rfc822, inline)]

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: Juri Linkov <juri <at> linkov.net>
Cc: 61712-close <at> debbugs.gnu.org
Subject: Re: bug#61712: 30.0.50; Want way to generate VC log for arbitrary
 list of files
Date: Wed, 22 Feb 2023 15:19:39 -0700

Hello,

On Wed 22 Feb 2023 at 09:07PM +02, Juri Linkov wrote:

>> Yesterday I wanted to review changes to some documentation files in a
>> repository; roughly, `git log -- dgit.1 *.pod`.  I would have preferred
>> to have the result in a *vc-log* buffer, but I don't believe we have a
>> command to do this.  'C-x v !' can't do it.
>>
>> If there were changes to each of the files, they would have appeared in
>> *vc-dir*, and I could have used the new vc-dir-mark-by-regexp, and then
>> vc-print-log would have done the right thing.
>>
>> So, I wonder if we could have a way to insert up-to-date files into
>> *vc-dir*, so that they could be used to select an arbitrary VC fileset?
>
> It's easy to do this in the Dired buffer by marking the required files.
> I'm doing this all the time since Dired supports all vc commands.

Oh, I didn't know dired could do this.  My apologies.

-- 
Sean Whitton

Previous Next

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