From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Gregory Heytings <gregory@heytings.org>,
Po Lu <luangruo@yahoo.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Stefan Kangas <stefan@marxist.se>,
emacs-devel@gnu.org
Subject: Re: A more radical cleanup for make bootstrap?
Date: Mon, 19 Sep 2022 20:49:23 +0000 [thread overview]
Message-ID: <YyjV08Gr2xrVJ9Qm@ACM> (raw)
In-Reply-To: <87mtavnm5m.fsf@gnus.org>
Hello, Lars.
On Mon, Sep 19, 2022 at 22:29:09 +0200, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > The prime quality of the current bootstrap is that it doesn't delete
> > anything unrecoverable - it only deletes generated files.
> But it does not delete all generated files, which is the problem. Try a
> "make bootstrap-clean" then "git clean -n -dfx" (note -- -n for dry run)
> to see the ones left behind.
If the choice is between failing to delete some generated files, and
deleting unrecoverable files, I'd take the first choice.
Is that the choice we're talking about, or are we talking about
deleting all generated files and no others?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-09-19 20:49 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 [this message]
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
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=YyjV08Gr2xrVJ9Qm@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).