From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Git help please - checking out old commit doesn't find lib/gnulib.mk.in.
Date: Sun, 12 Nov 2017 21:55:47 +0000 [thread overview]
Message-ID: <20171112215547.GD20916@ACM> (raw)
In-Reply-To: <b413979c-f623-f08f-b428-596d87fe7f04@cs.ucla.edu>
Hello, Paul.
On Sun, Nov 12, 2017 at 13:23:37 -0800, Paul Eggert wrote:
> Stefan Monnier wrote:
> > FWIW, I'm in Alan's camp: I can never remember which kind of "clean"
> > does what in the makefile.
> We could have a new rule ("make bootgit", say?) that does a "git clean -fdx"
> followed by a "make bootstrap". This rule would be useful only for developers
> who are using git.
And that would be utterly useless for me. I have quite a few
non-registered files around my repositories, for example those used by
backup scripts, or diff files, or stdout/stderr from Emacs builds.
I do not want to get rid of these random files. What I need to get rid
of are specifically those files which are preventing a build working.
From the documentation, you would expect make bootstrap to do this. It
doesn't. make clean and make distclean fail because around 12 files in
m4/ are missing. Why on earth are these make targets, which are solely
for deleting files, invoking m4 macros?
Why can Emacs not have a reliable way of cleaning up configuration and
build products (and _only_ these) such that a clean build can then be
done?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-11-12 21:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 18:09 Git help please - checking out old commit doesn't find lib/gnulib.mk.in Alan Mackenzie
2017-11-12 18:22 ` Andreas Schwab
2017-11-12 18:24 ` Óscar Fuentes
2017-11-12 18:25 ` Lele Gaifax
2017-11-12 18:28 ` John Wiegley
2017-11-12 18:29 ` Eli Zaretskii
2017-11-12 20:06 ` Alan Mackenzie
2017-11-12 20:28 ` Eli Zaretskii
2017-11-12 20:40 ` Stefan Monnier
2017-11-12 21:23 ` Paul Eggert
2017-11-12 21:55 ` Alan Mackenzie [this message]
2017-11-12 23:51 ` Óscar Fuentes
2017-11-13 1:58 ` Stefan Monnier
2017-11-13 2:34 ` Óscar Fuentes
2017-11-13 3:17 ` Stefan Monnier
2017-11-13 1:42 ` Yasushi SHOJI
2017-11-13 8:21 ` Andreas Schwab
2017-11-13 3:30 ` Eli Zaretskii
2017-11-13 18:53 ` Alan Mackenzie
2017-11-13 19:13 ` Paul Eggert
2017-11-13 19:31 ` Alan Mackenzie
2017-11-13 19:17 ` Eli Zaretskii
2017-11-13 19:27 ` Alan Mackenzie
2017-11-13 19:35 ` Eli Zaretskii
2017-11-13 20:30 ` Alan Mackenzie
2017-11-13 20:42 ` 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=20171112215547.GD20916@ACM \
--to=acm@muc.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).