all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Build failure on Windows
Date: Mon, 06 Mar 2017 18:08:55 +0200	[thread overview]
Message-ID: <83lgsiie08.fsf@gnu.org> (raw)
In-Reply-To: <58BD19A8.3040709@gmx.at> (message from martin rudalics on Mon, 06 Mar 2017 09:11:20 +0100)

> Date: Mon, 06 Mar 2017 09:11:20 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: andrewjmoreton@gmail.com, emacs-devel@gnu.org
> 
>  > I don't think master is broken, or that these things will become
>  > better in the future.
> 
> "These things" did not happen in the past ten years.
> 
>  > One recipe to avoid hitting these problems is
>  > to resync with upstream more often, because that minimizes the number
>  > of Lisp files that need to be recompiled, and lowers the probability
>  > of hitting some circular dependency with macros or somesuch.
> 
> I used to synch with master once a day on a regular basis.  I stopped
> doing that after build failures started to pile up.

Hmm... that's not my impression, I didn't see any significant changes
in build problems lately.  Maybe that's again because I build inside
the source tree.

Do you have any idea when things started deteriorating, per chance?



  reply	other threads:[~2017-03-06 16:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 10:20 Build failure on Windows martin rudalics
2017-03-05 11:03 ` Andy Moreton
2017-03-05 13:27   ` martin rudalics
2017-03-05 15:23     ` Eli Zaretskii
2017-03-05 17:59       ` martin rudalics
2017-03-05 18:32         ` martin rudalics
2017-03-05 20:03           ` Eli Zaretskii
2017-03-05 21:28             ` martin rudalics
2017-03-06  3:27               ` Eli Zaretskii
2017-03-06  8:10                 ` martin rudalics
2017-03-05 20:02         ` Eli Zaretskii
2017-03-05 21:28           ` martin rudalics
2017-03-05 21:38             ` Paul Eggert
2017-03-06  3:30               ` Eli Zaretskii
2017-03-06  3:29             ` Eli Zaretskii
2017-03-06  8:11               ` martin rudalics
2017-03-06 16:08                 ` Eli Zaretskii [this message]
2017-03-06 17:45                   ` martin rudalics
2017-03-06 18:48                     ` Eli Zaretskii
2017-03-07  9:45                       ` martin rudalics
2017-03-07 15:44                         ` Eli Zaretskii
2017-03-07 16:13                           ` martin rudalics
2017-03-07 16:23                             ` Eli Zaretskii
2017-03-05 15:19   ` Eli Zaretskii
2017-03-05 18:10     ` Andy Moreton
2017-03-05 20:06       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 18:28 Eric Hanchrow

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=83lgsiie08.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.