unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: sh.exe needed to bootstrap on Windows?
Date: Tue, 17 Jul 2007 01:01:15 +0300	[thread overview]
Message-ID: <ud4ysrot0.fsf@gnu.org> (raw)
In-Reply-To: <200707162130.l6GLUW4I014590@oogie-boogie.ics.uci.edu> (message from Dan Nicolaescu on Mon, 16 Jul 2007 14:30:32 -0700)

> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Date: Mon, 16 Jul 2007 14:30:32 -0700
> 
>   > 	(let ((backend (vc-file-getprop file 'vc-backend)))
>   > 	  (mapcar
>   > 	   (lambda (b)
>   > 	     (and (vc-call-backend b 'registered file)
>   > 		  (vc-file-setprop file 'vc-backend b)
>   > 		  (throw 'found t)))
>   > 	   (if (or (not backend) (eq backend 'none))
>   > 	       vc-handled-backends
>   > 	     (cons backend vc-handled-backends))))
>   > 
>   > Tries every backend in sight until it finds one.  
> 
> That is fine.
> 
>   > Am I missing something?
> 
> Don't know, vc-BACKEND-registered should be an autoloaded function
> that should not cause vc-BACKEND.el to be loaded.  So this code should
> not be the cause of vc-bzr.el being loaded.

But this is a mapcar that goes over vc-handled-backends, which
includes bzr.  So eventually, it will call

	       (vc-call-backend 'bzr file 'vc-backend)

which will load vc-bzr.el.  Am I right?

  reply	other threads:[~2007-07-16 22:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  9:10 sh.exe needed to bootstrap on Windows? Juanma Barranquero
2007-07-16 19:15 ` Eli Zaretskii
2007-07-16 19:54   ` Juanma Barranquero
2007-07-16 20:19     ` Eli Zaretskii
2007-07-16 20:28       ` Juanma Barranquero
2007-07-16 20:46         ` Eli Zaretskii
2007-07-16 21:01           ` Dan Nicolaescu
2007-07-16 21:19             ` Eli Zaretskii
2007-07-16 21:30               ` Dan Nicolaescu
2007-07-16 22:01                 ` Eli Zaretskii [this message]
2007-07-16 22:40                   ` Dan Nicolaescu
2007-07-16 22:44                     ` Eli Zaretskii
2007-07-16 22:53                       ` Dan Nicolaescu
2007-07-17  3:15                         ` Eli Zaretskii
2007-07-16 20:34       ` Dan Nicolaescu
2007-07-17  7:56       ` Jason Rumney
2007-07-17  8:43         ` Dan Nicolaescu
2007-07-17 11:26         ` Eli Zaretskii
2007-07-17 11:39           ` Juanma Barranquero
2007-07-17 11:45           ` Andreas Schwab
2007-07-17 12:51             ` Thien-Thi Nguyen
2007-07-17 13:13               ` David Kastrup
2007-07-17 20:02               ` Eli Zaretskii
2007-07-17 20:03             ` Eli Zaretskii
2007-07-17 16:52           ` Stefan Monnier
2007-07-17 20:06             ` Eli Zaretskii
2007-07-17 22:11               ` Juanma Barranquero
2007-07-16 22:47 ` Eli Zaretskii
2007-07-17 10:07   ` Juanma Barranquero
2007-07-17 10:33     ` Eli Zaretskii

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=ud4ysrot0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).