From: Gregory Heytings <gregory@heytings.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: acm@muc.de, larsi@gnus.org, luangruo@yahoo.com,
monnier@iro.umontreal.ca, stefan@marxist.se,
emacs-devel@gnu.org
Subject: Re: A more radical cleanup for make bootstrap?
Date: Tue, 20 Sep 2022 08:22:30 +0000 [thread overview]
Message-ID: <2b1180d2e511954365ca@heytings.org> (raw)
In-Reply-To: <E1oaWto-0002ia-6B@fencepost.gnu.org>
>> extraclean removes all generated files, and also all *~ and #* files.
>> If removing these files is a potential problem, they could perhaps be
>> kept by bootstrap (or be kept conditionally to some variable). But
>> note that *~ files are by default not created by Emacs, unless you've
>> set vc-make-backup-files to t in your init file.
>
> vc-make-backup-files only applies for files under version control,
> Non-version controlled files get backup files created by default.
>
> So if you have a file, not under version control, its backup files might
> get removed. That extraclean deletes files it does not know about (*~
> and #*) seems like a mis-feature.
>
After thinking a bit more about this, IMO these backup and autosaved files
can be kept by the new bootstrap-clean, given that it seems unlikely that
these files have an effect on the build, or at least that it is not more
likely that they could impact the build more than user-created files
(which aren't deleted by extraclean either).
next prev parent reply other threads:[~2022-09-20 8:22 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 [this message]
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=2b1180d2e511954365ca@heytings.org \
--to=gregory@heytings.org \
--cc=acm@muc.de \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.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).