unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Riccardo Murri" <riccardo.murri@gmail.com>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: vc-bzr bogosities
Date: Tue, 24 Jul 2007 10:53:20 -0400	[thread overview]
Message-ID: <jwvlkd53le6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1c34ba170707240637kd520dcg45ff29ead29050f3@mail.gmail.com> (Riccardo Murri's message of "Tue\, 24 Jul 2007 15\:37\:40 +0200")

>> > Note only isn't that a bzr dir, but I don't even _use_ bzr (though I
>> > have a .bar config file from a long time ago, which only has my email
>> > address in it).
>> 
>> I guess the above ".bar" was meant to be ".bzr" and is really ~/.bzr, right?
>> If so, that explains it: VC walks up the directory tree until it finds
>> a ".bzr" subdirectory and considers it to be the root of a BZR tree.
>> 
>> We need to make this determination more selective.  I don't know BZR nearly
>> well enough to know what should be done.  Would checking for
>> .bzr/branch-format be a good check (i.e. would it always succeed in a real
>> BZR workspace and would it normally fail in the ~/.bzr config dir)?
>> 

> That would probably be a workaround, although the only authoritative
> check would be to run `cd file-name-directory && bzr root` (but that
> slows vc-bzr down a lot).

Not just that, but the original problem is that running `bzr' signals errors
so my proposition is trying to reduce the cases where we need to run `bzr'.


        Stefan

  reply	other threads:[~2007-07-24 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 12:32 vc-bzr bogosities Miles Bader
2007-07-24 13:23 ` Stefan Monnier
2007-07-24 13:37   ` Riccardo Murri
2007-07-24 14:53     ` Stefan Monnier [this message]
2007-07-29 21:56 ` Dan Nicolaescu

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=jwvlkd53le6.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=riccardo.murri@gmail.com \
    /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).