From: Eli Zaretskii <eliz@gnu.org>
To: "Phillip Lord" <phillip.lord@russet.org.uk>
Cc: 23203@debbugs.gnu.org, Stromeko@nexgo.de
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 21:58:06 +0300 [thread overview]
Message-ID: <83fuv2plj5.fsf@gnu.org> (raw)
In-Reply-To: <3bf1141d622845eb4fe66b6dce573551.squirrel@cloud103.planethippo.com> (phillip.lord@russet.org.uk)
> Date: Sun, 3 Apr 2016 19:46:40 +0100
> From: "Phillip Lord" <phillip.lord@russet.org.uk>
> Cc: 23203@debbugs.gnu.org
>
> The attached patch fixes the problem in my hands (assuming we believe that
> this is a bug). The solution may be a bit blunt, though, although the
> function patched is documented as "use in batch during build".
Indeed, I'd rather we didn't do anything that drastic.
If needed, backups can be disabled from the command line.
next prev parent reply other threads:[~2016-04-03 18:58 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
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 [this message]
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
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=83fuv2plj5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23203@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
--cc=phillip.lord@russet.org.uk \
/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).