From: Stephen Berman <stephen.berman@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: vc-dir and Bazaar
Date: Fri, 23 Jul 2010 14:03:13 +0200 [thread overview]
Message-ID: <87r5iube2m.fsf@escher.home> (raw)
The Emacs manual (32.1 Version Control) says: "The Emacs version control
interface is called VC. Its commands work with several different
version control systems; currently, it supports GNU Arch, Bazaar, [...]"
and (32.1.6 VC Directory Mode): "The VC Directory buffer works with all
the version control systems that VC supports." But when I type `C-x v
d' (vc-dir) and at the prompt enter the directory of my bzr Emacs trunk
tree, all I get is this:
===============
VC backend : Bzr
Working dir: /data/steve/bzr/emacs/trunk/
Parent branch : http://bzr.savannah.gnu.org/r/emacs/trunk/
Shelves : No shelved changes
./
===============
No files are listed, although the parent branch contains changes against
my working directory. And when I type `+' (vc-update), all I get is the
message from vc-call-backend: "Sorry, merge-news is not implemented for
Bzr". (I don't understand the message; I thought I was invoking update,
not merge or merge-news, whatever that is.)
So does vc-dir not work with bzr, contrary to the manual, or do I need
to do something else? I have no problem using bzr from the command
line, updating the trunk, merging, etc. This is with
Bazaar (bzr) 2.1.0
Python interpreter: /usr/bin/python 2.6.2
Python standard library: /usr/lib/python2.6
Platform: Linux-2.6.31.12-0.2-default-i686-athlon-with-SuSE-11.2-i586
bzrlib: /usr/lib/python2.6/site-packages/bzrlib
Bazaar configuration: /home/steve/.bazaar
Bazaar log file: /home/steve/.bzr.log
and
GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.6) of
2010-07-18 on escher
I'd be grateful for any help.
Steve Berman
next reply other threads:[~2010-07-23 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 12:03 Stephen Berman [this message]
2010-07-23 21:32 ` vc-dir and Bazaar Óscar Fuentes
2010-07-23 21:45 ` Stephen Berman
2010-07-24 7:47 ` Eli Zaretskii
2010-07-24 11:56 ` Stephen Berman
2010-07-24 12:21 ` Eli Zaretskii
2010-07-24 16:20 ` Stephen Berman
2010-07-24 16:52 ` Eli Zaretskii
2010-07-29 13:33 ` Stephen Berman
2010-07-24 15:32 ` Óscar Fuentes
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=87r5iube2m.fsf@escher.home \
--to=stephen.berman@gmx.net \
--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).