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 11:43:42 +0300 [thread overview]
Message-ID: <uprswaiip.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0804101524k2ad4f9a8m8a06889bfbfa0af2@mail.gmail.com>
> Date: Fri, 11 Apr 2008 00:24:51 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: jasonr@gnu.org, emacs-devel@gnu.org
>
> On Thu, Apr 10, 2008 at 9:52 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Usually, update-subdirs is just a waste of time, since new directories
> > are seldom created.
>
> Well, I'd say the point of cvs-update is to be correct over fast,
> isn't it?
No, it isn't. If you want to be correct, use "make bootstrap".
cvs-update was introduced as a very useful shortcut, which takes half
a minute, if only a few Lisp files were modified, rather than one and
a half hour taken by bootstrapping.
> And as Jason points out, it is a negligible amount of time
> anyway.
One (minor) problem is that it regenerates subdirs.el unconditionally,
so whatever targets that depend on it will be remade as well.
But these are all minor considerations, admittedly.
next prev parent reply other threads:[~2008-04-11 8:43 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 [this message]
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
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=uprswaiip.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 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).