From: Achim Gratz <Stromeko@nexgo.de>
To: 23203@debbugs.gnu.org
Subject: bug#23203: 25.0.91; some loaddefs files have auto-save remnants after building (and install doesn't ignore them)
Date: Sun, 03 Apr 2016 10:48:29 +0200 [thread overview]
Message-ID: <87shz35b8i.fsf@Rainer.invalid> (raw)
In-Reply-To: <87twjjqidp.fsf@Rainer.invalid>
Andreas Schwab writes:
> Achim Gratz writes:
>> Moreover, these will be copied into the installation.
> No, they aren't, see line 598 of Makefile.in:
>
> rm -f $${subdir}/*~ ; \
That is where they are getting removed after already having been
installed. They shouldn't get created or installed in the first place,
as there is no point of having a backup for an auto-generated file.
On another tangent, is it really necessary to invoke another rm for each
file pattern to delete?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2016-04-03 8:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 7:08 bug#23203: 25.0.91; some loaddefs files have auto-save remnants after building (and install doesn't ignore them) Achim Gratz
2016-04-03 8:26 ` Andreas Schwab
2016-04-03 8:28 ` Andreas Schwab
2016-04-03 8:48 ` Achim Gratz [this message]
2016-04-03 10:46 ` Andreas Schwab
2016-04-03 11:47 ` Achim Gratz
2016-04-03 13:58 ` Phillip Lord
2016-04-03 14:36 ` Andreas Schwab
2016-04-03 18:46 ` Phillip Lord
2016-04-03 18:58 ` Eli Zaretskii
2016-04-03 19:33 ` Phillip Lord
2016-04-03 19:39 ` Eli Zaretskii
2016-04-03 20:11 ` Phillip Lord
2016-04-04 15:27 ` Eli Zaretskii
2016-04-04 22:12 ` Phillip Lord
2016-04-05 18:16 ` Achim Gratz
2016-04-08 8:22 ` Eli Zaretskii
2016-04-08 15:25 ` Phillip Lord
2016-04-10 20:30 ` Phillip Lord
2016-04-12 12:03 ` Phillip Lord
2016-04-12 15:20 ` Eli Zaretskii
2016-04-12 15:39 ` Glenn Morris
2016-04-12 16:34 ` Phillip Lord
2016-04-12 16:40 ` Eli Zaretskii
2016-04-12 18:08 ` John Wiegley
2020-08-15 4:11 ` Stefan Kangas
2016-04-04 15:42 ` Achim Gratz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shz35b8i.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=23203@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.