all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: [Emacs-diffs] Changes to emacs/nt/INSTALL,v
Date: Fri, 11 Apr 2008 17:40:10 +0300	[thread overview]
Message-ID: <uiqyoa20l.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0804110346y7e838fbfi2b8bf6b7cda83774@mail.gmail.com>

> Date: Fri, 11 Apr 2008 12:46:03 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: jasonr@gnu.org, emacs-devel@gnu.org
> 
> On Fri, Apr 11, 2008 at 12:22 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >  > Hm. I would've said that the whole point of cvs-update is to be more
> >  > correct than recompile; else, why not simply use recompile, which is
> >  > faster?
> >
> >  Because without the other prerequisites of cvs-update, especially
> >  autoloads, you will have a buggy Emacs.
> 
> I thought that was implied in "to be more correct than recompile" ;-)

It is more correct, but it does not aim to be absolutely correct.  It
is okay for it to fail in rare situations, if that saves a significant
amount of time.




      reply	other threads:[~2008-04-11 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Jjscj-0002sL-1T@cvs.savannah.gnu.org>
2008-04-10  9:36 ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Juanma Barranquero
2008-04-10  9:50   ` Jason Rumney
2008-04-10 17:53     ` Recommended build procedure [was Re: [Emacs-diffs] Changes to emacs/nt/INSTALL, v] Glenn Morris
2008-04-10 19:52   ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Eli Zaretskii
2008-04-10 20:21     ` Jason Rumney
2008-04-10 22:24     ` Juanma Barranquero
2008-04-11  8:43       ` Eli Zaretskii
2008-04-11  9:13         ` Juanma Barranquero
2008-04-11 10:22           ` Eli Zaretskii
2008-04-11 10:46             ` Juanma Barranquero
2008-04-11 14:40               ` Eli Zaretskii [this message]

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=uiqyoa20l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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 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.