From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>,
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:31:46 +0000 [thread overview]
Message-ID: <20171113193146.GC3952@ACM> (raw)
In-Reply-To: <9ba6a5a2-d829-ad98-44a5-88d0191f1edd@cs.ucla.edu>
Hello, Paul.
On Mon, Nov 13, 2017 at 11:13:53 -0800, Paul Eggert wrote:
> On 11/13/2017 10:53 AM, Alan Mackenzie wrote:
> > make distclean is broken. It purports to remove all files generated by
> > "configuring or building the program".
> The intent is that 'make distclean' gets you back to a distribution
> tarball, if all you've done is 'configure; make'. But that doesn't seem
> to be what you're asking for. If I understand you correctly, you want
> something that gets you back to a fresh git checkout if all you've done
> is './autogen.sh; ./configure; make', and since 'make distclean' doesn't
> do what you're asking for, you're saying it's broken. If I'm right, it
> would be more accurate to say that 'make distclean' is simply a tool
> that doesn't do what you want.
It's a tool that doesn't do what it says on the tin. What it says is:
# make distclean
# Delete all files from the current directory that are created by
# configuring or building the program. If you have unpacked the
# source and built the program without creating any other files,
# 'make distclean' should leave only the files that were in the
# distribution.
What it doesn't say is "Delete all files ..... or building the program,
which were created from an Emacs distribution."
> Perhaps someone (you?) could implement a 'make gitclean' that does what
> you want.
Well, first I'll follow Eli's suggestion and try make extraclean.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-11-13 19:31 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 [this message]
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=20171113193146.GC3952@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).