all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffstrunk r117208: * lisp/files.el (locate-dominating-file): Expand file argument.
Date: Sun, 01 Jun 2014 19:59:19 +0200	[thread overview]
Message-ID: <87iooko6iw.fsf@gmx.de> (raw)
In-Reply-To: <hmppispmq9.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 01 Jun 2014 13:23:58 -0400")

Glenn Morris <rgm@gnu.org> writes:

> It will be harmless to set BZR_HOME if something other than bzr is used.
> But you should be able to make the setting conditional on bzr being
> chosen, if you like. (I could not figure out if I needed to modify
> process-environment or tramp-remote-process-environment, and if the
> latter needed to be changed early on.)

It's tramp-remote-process-environment. I'll set it in
tramp-test29-vc-registered with my next commit.

>> OTOH, it's not guaranteed that all people have set BZR_HOME.
>
> I don't understand.

I meant that bzr could behave different, depending whether BZR_HOME is
set, or not. Don't know.

But *this* is not the purpose of tramp-test29-vc-registered. If needed
it could be tested in vc-bzr-test*.

Now I have tons of traces on hydra. I'll dig through them, until I'll
see what happens. Unfortunately, this problem does not occur in my local
Emacs trunk stanza.

Best regards, Michael.



  reply	other threads:[~2014-06-01 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WqZ19-0003OV-AT@vcs.savannah.gnu.org>
2014-05-31 19:27 ` Emacs-diffstrunk r117208: * lisp/files.el (locate-dominating-file): Expand file argument Glenn Morris
2014-06-01  7:50   ` Michael Albinus
2014-06-01 17:23     ` Glenn Morris
2014-06-01 17:59       ` Michael Albinus [this message]
2014-06-01 22:22         ` Glenn Morris
2014-06-02 18:42           ` Michael Albinus

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=87iooko6iw.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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 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.