From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 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: Mon, 13 Nov 2017 19:27:04 +0000 [thread overview]
Message-ID: <20171113192704.GB3952@ACM> (raw)
In-Reply-To: <83k1yukmy2.fsf@gnu.org>
Hello, Eli.
On Mon, Nov 13, 2017 at 21:17:41 +0200, Eli Zaretskii wrote:
> > Date: Mon, 13 Nov 2017 18:53:43 +0000
> > Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > > > make clean and make distclean fail because around 12 files in m4/
> > > > are missing.
> > > These targets should be invoked _before_ checking out another
> > > revision, not after. Otherwise, you get a bunch of Makefile's that
> > > are inconsistent with the working tree contents.
> > Yes, that works better, thanks. But not perfectly.
> You want extraclean instead, and if that isn't perfect either, it
> needs to be fixed to remove whatever it fails to remove.
> > make distclean is broken.
> No, it isn't. "make distclean" is for when you build from a release
> tarball, not when you build from Git after checking out a different
> version of the tree.
OK, let me correct that: "make distclean's documentation is unclear". It
fails to state clearly what you've just said.
But I'll have a go at make extraclean, now.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-11-13 19:27 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
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 [this message]
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=20171113192704.GB3952@ACM \
--to=acm@muc.de \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).