From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 5291@debbugs.gnu.org
Subject: bug#5291: 23.1.91; "bzr status" FAILED
Date: Sun, 03 Jan 2010 06:09:58 +0200 [thread overview]
Message-ID: <83637jesmh.fsf@gnu.org> (raw)
In-Reply-To: <201001022217.o02MHUE3013455@godzilla.ics.uci.edu>
> Date: Sat, 2 Jan 2010 14:17:30 -0800 (PST)
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Cc: 5291@debbugs.gnu.org
>
> What exactly creates the d:/gnu/bzr/emacs/trunk/bzr_log.ahvp69 file?
"bzr commit" does. This file is where it puts the list of files to be
committed, then submits it to $EDITOR (in my case, emacsclient), and
expects me to insert the commit message there. After "bzr commit" is
done (i.e., the changes committed), this file is deleted by bzr.
> Is your TEMP set to d:/gnu/bzr/emacs/trunk/ ?
No. AFAIU, bzr creates these temporary files in the directory where
you run "bzr commit". I see these files created in the current
directory on GNU/Linux as well, although I will have to check if the
same problem happens there as well as on Windows.
> I think that if you change:
> (vc-bzr-command "status" t 0 file)
> to:
> (vc-bzr-command "status" t 3 file)
> in vc-bzr-status
> it should work, but I am not 100% sure that's TRTD.
OK, I will look into this when I have a chance. Thanks.
Do you (or someone else) know where can I find the documentation of
status code returned by bzr?
next prev parent reply other threads:[~2010-01-03 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83637baejr.fsf@gnu.org>
2010-01-02 17:43 ` bug#5291: 23.1.91; "bzr status" FAILED Eli Zaretskii
2010-01-02 20:47 ` Dan Nicolaescu
2010-01-02 21:40 ` Eli Zaretskii
2010-01-02 21:56 ` Lennart Borgman
2010-01-02 22:17 ` Dan Nicolaescu
2010-01-03 4:09 ` Eli Zaretskii [this message]
2010-01-03 18:39 ` Eli Zaretskii
2010-01-03 20:10 ` Dan Nicolaescu
2010-01-09 8:07 ` bug#5291: marked as done (23.1.91; "bzr status" FAILED) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83637jesmh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5291@debbugs.gnu.org \
--cc=dann@ics.uci.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.