From: Dmitry Gutov <dgutov@yandex.ru>
To: andrea crotti <andrea.crotti.0@gmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: No VC backend is responsible for
Date: Thu, 21 May 2015 13:31:41 +0300 [thread overview]
Message-ID: <555DB40D.4080509@yandex.ru> (raw)
In-Reply-To: <CAF_E5Jak73E0QZf-7uUhVFfWWnjhWi_a1H7riOJUNpHeUpJwiQ@mail.gmail.com>
On 05/21/2015 01:25 PM, andrea crotti wrote:
> Yes that works well thanks a lot,
> I guess the implementation of vc-working-revision changed or I always
> had this issue and I never realised.
It was changed on March 1 in 7f9b037245ddb662ad98685e429a2498ae6b7c62,
to make the function return non-nil on ignored and unregistered files
(inside a VCS repository).
next prev parent reply other threads:[~2015-05-21 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 9:02 No VC backend is responsible for andrea crotti
2015-05-21 9:22 ` Dmitry Gutov
2015-05-21 9:41 ` andrea crotti
2015-05-21 9:55 ` Tassilo Horn
2015-05-21 10:25 ` andrea crotti
2015-05-21 10:31 ` Dmitry Gutov [this message]
2015-05-21 10:32 ` Tassilo Horn
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=555DB40D.4080509@yandex.ru \
--to=dgutov@yandex.ru \
--cc=andrea.crotti.0@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).