unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 08 Apr 2016 16:25:09 +0100	[thread overview]
Message-ID: <87y48oi0mi.fsf@russet.org.uk> (raw)
In-Reply-To: <83oa9kjyqt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Apr 2016 11:22:50 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Cc: 23203@debbugs.gnu.org,  stromeko@nexgo.de
>> Date: Mon, 04 Apr 2016 23:12:57 +0100
>> Also, it sounds reasonable -- I've attached a patch with a variation on
>> this theme.
>
> Thanks.  There seem to be spurious unrelated whitespace changes in the
> patch.

Yeah, it was a proof-of-concept patch. It's got some debug statements in
also.

Alas, it also seems to have a bootstrap bug. Will work on it.

>> So, we need to make sure that the packaging system does not copy backup
>> files.
>
> "make install" already removes backup files from the target tree, so
> is there any problem left?

Ah, okay, that's fine; I'll work on my patch and try and get it actually
working.

Phil





  reply	other threads:[~2016-04-08 15:25 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
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 [this message]
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=87y48oi0mi.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=23203@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stromeko@nexgo.de \
    /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).