From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: theophilusx@gmail.com, emacs-devel@gnu.org
Subject: Re: Git master head build failure?
Date: Thu, 01 Apr 2021 16:07:56 +0300 [thread overview]
Message-ID: <835z16gnkj.fsf@gnu.org> (raw)
In-Reply-To: <jwvsg4a5fcq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 01 Apr 2021 09:03:53 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: theophilusx@gmail.com, emacs-devel@gnu.org
> Date: Thu, 01 Apr 2021 09:03:53 -0400
>
> > This should be added to the 'extraclean' target, IMO (together with
> > all the other generated files in lisp/cedet).
>
> I can never remember which clean target does what (and reading their
> description has usually not been sufficient to be able to predict which
> files would remain when I wasn't sure). Luckily I don't think it
> matters much because I never invoke such targets.
>
> But what does matter is what happens when we `make bootstrap`, because
> this is a much more common need than `make maintainer-clean` or `make
> extraclean`.
I never use "make bootstrap": does that mean it isn't important
either? ;-)
Seriously, though: this depends on your workflows. AFAIU most people
do "make bootstrap" to solve problems with Lisp macro expansions, and
for that forcing them to regenerate every single file that isn't
versioned is not the best idea. If you want to start from a pristine
clone, just clone a new worktree.
next prev parent reply other threads:[~2021-04-01 13:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 2:41 Git master head build failure? Tim Cross
2021-04-01 3:04 ` Stefan Monnier
2021-04-01 3:10 ` Tim Cross
2021-04-01 7:33 ` Eli Zaretskii
2021-04-01 8:57 ` Tim Cross
2021-04-01 9:17 ` tomas
2021-04-01 9:56 ` Daniel Brooks
2021-04-01 9:36 ` Gregor Zattler
2021-04-01 10:11 ` Andreas Schwab
2021-04-01 7:25 ` Eli Zaretskii
2021-04-01 8:34 ` Tim Cross
2021-04-01 9:00 ` Eli Zaretskii
2021-04-01 10:56 ` Stefan Kangas
2021-04-01 13:03 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:02 ` Eli Zaretskii
2021-04-01 13:01 ` Eli Zaretskii
2021-04-01 13:03 ` Stefan Monnier
2021-04-01 13:07 ` Eli Zaretskii [this message]
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:36 ` Eli Zaretskii
2021-04-01 15:32 ` Stefan Monnier
2021-04-01 15:37 ` Eli Zaretskii
2021-04-01 16:05 ` extraclean and admin/grammars [was Re: Git master head build failure?] Glenn Morris
2021-04-01 16:09 ` Lars Ingebrigtsen
2021-04-01 16:19 ` Lars Ingebrigtsen
2021-04-02 4:19 ` Tim Cross
2021-04-02 5:58 ` Eli Zaretskii
2021-04-02 13:41 ` Lars Ingebrigtsen
2021-04-02 13:58 ` Eli Zaretskii
2021-04-01 18:31 ` Eli Zaretskii
2021-04-02 13:40 ` Lars Ingebrigtsen
2021-04-02 13:57 ` Eli Zaretskii
2021-04-03 13:30 ` Lars Ingebrigtsen
2021-04-03 14:15 ` Eli Zaretskii
2021-04-03 22:36 ` chad
2021-04-04 7:20 ` Eli Zaretskii
2021-04-03 23:52 ` Tim Cross
2021-04-04 7:39 ` Eli Zaretskii
2021-04-04 19:44 ` Lars Ingebrigtsen
2021-04-01 17:15 ` Stefan Monnier
2021-04-01 19:56 ` Eli Zaretskii
2021-04-01 20:13 ` Stefan Monnier
2021-04-03 7:58 ` Eli Zaretskii
2021-04-13 2:20 ` Stefan Monnier
2021-04-13 11:51 ` Eli Zaretskii
2021-04-13 12:19 ` Eli Zaretskii
2021-04-13 13:01 ` Stefan Monnier
2021-04-13 12:59 ` Stefan Monnier
2021-04-13 14:03 ` Eli Zaretskii
2021-04-01 18:29 ` Eli Zaretskii
2021-04-04 16:28 ` Glenn Morris
2021-04-04 17:12 ` 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=835z16gnkj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=theophilusx@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).