unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 12001@debbugs.gnu.org
Subject: bug#12001: 24.1.50; vc-diff always talks to CVS repository
Date: Sun, 19 Aug 2012 18:29:58 -0400	[thread overview]
Message-ID: <E1T3E0M-0003mj-08@fencepost.gnu.org> (raw)
In-Reply-To: <m2ipdh4k71.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 21 Jul 2012 10:01:06 +0200)

    >     I cannot reproduce that.  When the vc backup file for the current
    >     revision exists, vc-diff uses it as the base.

    > What is the "vc backup file"?  How can I tell whether it exists?

    See vc-version-backup-file-name.  They are created the first time the
    modified file is saved.

This is not happening for me when I edit the Emacs sources.
The reason seems to be that 

           (vc-call-backend backend 'make-version-backups-p file)

does nothing, because it calls vc-default-make-version-backups-p
which always returns nil.

This is because (get 'Bzr 'vc-functions)
returns the following:

((make-version-backups-p vc-default-make-version-backups-p . Bzr) (checkout-model . vc-bzr-checkout-model) (registered . vc-bzr-registered) (find-file-hook . vc-bzr-find-file-hook) (working-revision . vc-bzr-working-revision) (state-heuristic . vc-bzr-state-heuristic) (mode-line-string vc-default-mode-line-string . Bzr))

Indeed, vc-bzr-make-version-backups-p is not defined.
Should it be?

--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call






  reply	other threads:[~2012-08-19 22:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 18:45 bug#12001: 24.1.50; vc-diff always talks to CVS repository Richard Stallman
2012-07-20 19:10 ` Andreas Schwab
2012-07-21  2:43   ` Richard Stallman
2012-07-21  8:01     ` Andreas Schwab
2012-08-19 22:29       ` Richard Stallman [this message]
2012-08-20  7:25         ` Andreas Schwab
2012-08-21  2:20           ` Richard Stallman
2012-08-21  2:52             ` Eli Zaretskii
2012-08-21  3:53               ` Glenn Morris
2012-08-21 21:22                 ` Richard Stallman
2012-08-22  2:56                   ` Eli Zaretskii
2012-08-22  3:13                     ` Glenn Morris
2012-08-22 16:26                       ` Eli Zaretskii
2012-08-22 16:33                         ` Glenn Morris
2012-08-23  2:49                       ` Richard Stallman
2012-08-23  7:09                         ` Glenn Morris
2012-08-23  7:14                           ` Glenn Morris
2012-08-23  7:16                             ` Glenn Morris
2012-08-23  8:18                           ` Paul Eggert
2012-08-24  2:17                             ` Richard Stallman
2012-08-24  4:06                               ` Paul Eggert

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=E1T3E0M-0003mj-08@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=12001@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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.
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).