From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, raeburn@raeburn.org, 26459@debbugs.gnu.org
Subject: bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull"
Date: Fri, 14 Apr 2017 13:08:39 -0400 [thread overview]
Message-ID: <q8a87i29yg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83shlbh2t1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Apr 2017 10:21:46 +0300")
Eli Zaretskii wrote:
> I think this is the right direction, but I can only wonder how come
> this problem didn't come up before. I'm building with -j6 and -j8 for
> a very long time, and never saw such failures, although clearly the
> generated unidata files might not yet exist when loaddefs.el is
> produced. Is this likely to happen only on slow machines?
I was wondering the same thing and could only come up with the same
hypothesis. :)
(I also wondered if this indicates another area where atomic writes
would help.)
next prev parent reply other threads:[~2017-04-14 17:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 8:54 bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Eli Zaretskii
2017-04-12 15:58 ` Glenn Morris
2017-04-12 16:03 ` Eli Zaretskii
2017-04-12 16:43 ` Glenn Morris
2017-04-12 18:09 ` Glenn Morris
2017-04-13 7:06 ` Eli Zaretskii
2017-04-13 9:03 ` Ken Raeburn
2017-04-13 22:44 ` Paul Eggert
2017-04-14 1:08 ` Glenn Morris
2017-04-14 7:21 ` Eli Zaretskii
2017-04-14 17:08 ` Glenn Morris [this message]
2017-04-15 1:25 ` Glenn Morris
2017-04-15 7:30 ` Eli Zaretskii
2017-04-26 18:32 ` Glenn Morris
2017-04-26 20:24 ` Paul Eggert
2017-04-26 20:37 ` bug#26459: 26.0.50; loaddefs.el is regenerated after each 'git pull' Phillip Lord
2017-04-26 20:47 ` bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Glenn Morris
2017-04-12 21:37 ` Paul Eggert
2017-04-13 7:09 ` 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=q8a87i29yg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=26459@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=raeburn@raeburn.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 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).