From: Eli Zaretskii <eliz@gnu.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: emacs-devel@gnu.org
Subject: Re: A more radical cleanup for make bootstrap?
Date: Tue, 20 Sep 2022 19:21:18 +0300 [thread overview]
Message-ID: <834jx2vwxt.fsf@gnu.org> (raw)
In-Reply-To: <875yhi3tw7.fsf@md5i.com> (message from Michael Welsh Duggan on Tue, 20 Sep 2022 12:14:32 -0400)
> From: Michael Welsh Duggan <mwd@md5i.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 20 Sep 2022 12:14:32 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> What about me?
> >>
> >> It generally takes 10-15 minutes for me to build Emacs in ideal
> >> conditions from "make bootstrap", with much of that time taken up by
> >> building temacs. It takes longer when I am actually working on Emacs,
> >> because that typically happens while my machine is already under load.
> >
> > Why do you bootstrap?
> >
> > I almost never do that.
>
> Personally, I almost always bootstrap.
That's fine, but my question was specifically to Po Lu (and people who
work on Emacs like he does), who builds Emacs much more frequently
than you do. Your case is different, and the existing"make bootstrap"
covers it well enough, AFAIU.
prev parent reply other threads:[~2022-09-20 16:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 19:46 A more radical cleanup for make bootstrap? Gregory Heytings
2022-09-19 19:48 ` Lars Ingebrigtsen
2022-09-19 20:26 ` Alan Mackenzie
2022-09-19 20:29 ` Lars Ingebrigtsen
2022-09-19 20:49 ` Alan Mackenzie
2022-09-19 20:51 ` Lars Ingebrigtsen
2022-09-19 21:01 ` Alan Mackenzie
2022-09-20 2:35 ` Eli Zaretskii
2022-09-20 2:42 ` Po Lu
2022-09-20 11:01 ` Eli Zaretskii
2022-09-20 10:01 ` Alan Mackenzie
2022-09-19 21:45 ` Gregory Heytings
2022-09-20 6:38 ` Alfred M. Szmidt
2022-09-20 8:22 ` Gregory Heytings
2022-09-19 20:53 ` Stefan Monnier
2022-09-20 2:29 ` Eli Zaretskii
2022-09-20 7:58 ` Gregory Heytings
2022-09-20 8:20 ` Po Lu
2022-09-20 8:25 ` Gregory Heytings
2022-09-20 8:46 ` Po Lu
2022-09-20 9:01 ` Gregory Heytings
2022-09-20 11:22 ` Eli Zaretskii
2022-09-20 11:55 ` Po Lu
2022-09-20 12:05 ` Eli Zaretskii
2022-09-20 12:51 ` Po Lu
2022-09-20 12:55 ` Eli Zaretskii
2022-09-20 13:08 ` Lars Ingebrigtsen
2022-09-20 13:27 ` Po Lu
2022-09-20 13:31 ` Lars Ingebrigtsen
2022-09-20 14:00 ` Eli Zaretskii
2022-09-20 15:54 ` Eli Zaretskii
2022-09-20 16:46 ` Michael Albinus
2022-09-21 2:16 ` Po Lu
2022-09-20 15:43 ` Robert Pluim
2022-09-20 15:55 ` Eli Zaretskii
2022-09-20 16:14 ` Michael Welsh Duggan
2022-09-20 16:21 ` 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
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=834jx2vwxt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mwd@md5i.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).