From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: vc-dir does not show missing revisions for bzr
Date: Thu, 03 Feb 2011 14:41:45 -0500 [thread overview]
Message-ID: <svd3n8dhxi.fsf@tbox.m2.algo> (raw)
In-Reply-To: yxqtygl3xei.fsf@fencepost.gnu.org
> * Dan Nicolaescu <qnaa@tah.bet> [2011-02-03 11:17:41 -0500]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> GNU Emacs 24.0.50.7 (x86_64-unknown-linux-gnu, GTK+ Version 2.10.4)
>> of 2011-02-02 on tbox
>>
>> vc-dir for cvs & svn show "need-update" status for file which would be
>> changed by the next `vc-pull'.
>> it would be nice if bzr/hg/git did the same.
>
> vc-dir just displays the results of cvs/svn status".
> If there's a command/sequence of commands that can produce the list of
> files you want, then vc-dir could be changed to show it.
yeah, here the fundamental difference between cvs/svn and hg/git/bzr
strikes again...
> [Not exactly the same thing, but using C-x v I shows the list of
> upstream changes...]
cool, thanks!
alas, it creates a *vc-incoming* buffer where "D" does not work:
the *vc-diff* buffer says:
bzr: ERROR: Requested revision: u'103104' does not exist in branch: BzrBranch7('file:///home2/sds/src/emacs/trunk/')
PS. I am seeing these all the time: C-x v d
Debugger entered--Lisp error: (error "Running bzr shelve --list -q ....FAILED (status 3)")
signal(error ("Running bzr shelve --list -q ....FAILED (status 3)"))
error("Running %s...FAILED (%s)" "bzr shelve --list -q ." "status 3")
vc-do-command(#<buffer *temp*> 1 "bzr" nil "shelve" "--list" "-q")
apply(vc-do-command #<buffer *temp*> 1 "bzr" nil "shelve" ("--list" "-q"))
vc-bzr-command("shelve" #<buffer *temp*> 1 nil "--list" "-q")
vc-bzr-shelve-list()
vc-bzr-dir-extra-headers("/home2/sds/src/emacs/trunk/")
apply(vc-bzr-dir-extra-headers "/home2/sds/src/emacs/trunk/")
vc-call-backend(Bzr dir-extra-headers "/home2/sds/src/emacs/trunk/")
vc-dir-headers(Bzr "/home2/sds/src/emacs/trunk/")
vc-dir-refresh()
vc-dir-mode()
vc-dir("/home2/sds/src/emacs/trunk/" nil)
call-interactively(vc-dir nil nil)
(insert-buffer " *temp*")
bzr: ERROR: Could not acquire lock "/home2/sds/src/emacs/trunk/.bzr/checkout/dirstate": [Errno 11] Resource temporarily unavailable
--
Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final)
http://dhimmi.com http://openvotingconsortium.org http://thereligionofpeace.com
http://iris.org.il http://www.memritv.org http://truepeace.org http://ffii.org
Democrats, get out of my wallet! Republicans, get out of my bedroom!
next prev parent reply other threads:[~2011-02-03 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 21:25 vc-dir does not show missing revisions for bzr Sam Steingold
2011-02-03 16:17 ` Dan Nicolaescu
2011-02-03 19:41 ` Sam Steingold [this message]
2011-02-03 21:22 ` Eli Zaretskii
2011-02-03 22:00 ` Sam Steingold
2011-02-04 8:19 ` Eli Zaretskii
2011-02-04 16:57 ` Dan Nicolaescu
2011-02-04 21:16 ` Stefan Monnier
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=svd3n8dhxi.fsf@tbox.m2.algo \
--to=sds@gnu.org \
--cc=emacs-devel@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).