unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: michael_heerdegen@web.de, emacs-devel@gnu.org
Subject: Re: How to get a list of changed files with VC?
Date: Sat, 15 Jul 2017 20:52:57 +0300	[thread overview]
Message-ID: <83pod1egee.fsf@gnu.org> (raw)
In-Reply-To: <0571a5da-53a5-7b26-fd8e-c3981d7d154c@yandex.ru> (message from Dmitry Gutov on Sat, 15 Jul 2017 20:41:29 +0300)

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 15 Jul 2017 20:41:29 +0300
> 
> On 7/13/17 4:23 AM, Michael Heerdegen wrote:
> 
> > More specific questions about my implementation:
> > 
> > 1.  The implementation of the first function
> > `el-search--changed-files-in-repo' is currently git-specific, but I
> > didn't find a way to implement it with functions that VC defines to make
> > it work for other version control systems.  Any idea?
> 
> For the changed files relative to HEAD, you can call the backend command 
> (with vc-call-backend) named dir-status-files. But there is no way to 
> specify the reference revision.

Maybe we should extend dir-status-files to accept a version, or even a
range of versions.

> Maybe calling the VC backend diff command on the whole repo and
> parsing the output could work.

I think Git is the odd one out providing this information as a
side-effect of a diff command (with a option that makes little sense
for a diff command).  All the other back-ends I know of provide the
info as part of the status command.  I think.



  reply	other threads:[~2017-07-15 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  1:23 How to get a list of changed files with VC? Michael Heerdegen
2017-07-15 17:41 ` Dmitry Gutov
2017-07-15 17:52   ` Eli Zaretskii [this message]
2017-07-16 17:12     ` Dmitry Gutov
2017-07-16 17:40       ` Eli Zaretskii
2017-07-16 17:45         ` Dmitry Gutov
2017-07-16 17:49           ` Eli Zaretskii
2017-07-16 17:59             ` Dmitry Gutov
2017-07-19  0:37   ` Michael Heerdegen

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=83pod1egee.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).