all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 61712@debbugs.gnu.org
Subject: bug#61712: 30.0.50; Want way to generate VC log for arbitrary list of files
Date: Wed, 22 Feb 2023 21:07:39 +0200	[thread overview]
Message-ID: <86o7plplhg.fsf@mail.linkov.net> (raw)
In-Reply-To: <871qmhd339.fsf@melete.silentflame.com> (Sean Whitton's message of "Wed, 22 Feb 2023 10:25:46 -0700")

> 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.





  reply	other threads:[~2023-02-22 19:07 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 [this message]
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

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=86o7plplhg.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=61712@debbugs.gnu.org \
    --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.