From: Glenn Morris <rgm@gnu.org>
To: rms@gnu.org
Cc: 12001@debbugs.gnu.org
Subject: bug#12001: 24.1.50; vc-diff always talks to CVS repository
Date: Mon, 20 Aug 2012 23:53:49 -0400 [thread overview]
Message-ID: <5vtxvw529e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83vcgdardy.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Aug 2012 05:52:09 +0300")
Firstly;
Is this bug report about CVS, as the initial report and subject
indicate; or is it about bzr, as every subsequent message seems to
indicate? If so, bzr + vc-diff + no network works just fine for me.
Eli Zaretskii wrote:
> Since bzr has all the history of the versions locally
Secondly;
Maybe rms has somehow ended up with a lightweight checkout, or a stacked
branch, or some other non-standard form of bzr repository that does not
actually keep all the data locally.
What does `bzr info' report in the local copy?
While Emacs could in principle try to handle these forms of bzr checkout
better, it seems kind of pointless, since the solution is simply to use
a "normal" bzr branch.
next prev parent reply other threads:[~2012-08-21 3:53 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
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 [this message]
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=5vtxvw529e.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12001@debbugs.gnu.org \
--cc=rms@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.
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).