unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Klaus.Zeitler@alcatel-lucent.com,
	Paul Eggert <eggert@cs.ucla.edu>,
	16717@debbugs.gnu.org
Subject: bug#16717: Dumping: Can't update subspace record
Date: Fri, 14 Feb 2014 12:31:52 -0500	[thread overview]
Message-ID: <jwv7g8xob7t.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <ovfvnmrv24.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 14 Feb 2014 02:51:31 -0500")

>> Stefan "who'd rather require GNU Make"
> You would? Really and truly? For some reason I thought you were against that.

AFAIK GNU Make is available everywhere where Emacs can be built.
So while requiring GNU Make might occasionally be a hindrance because
the user has to first install GNU Make, it would not prevent
building Emacs.

For that reason, I'm not opposed to it.

> Because I totally agree; and I think we should do that post 24.4.
> It will make Makefile life much easier.

Let's move this to emacs-devel to see if someone has a good reason to
oppose it.


        Stefan





  reply	other threads:[~2014-02-14 17:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <q5glhxj886p.fsf@destgd0h411156.de.alcatel-lucent.com>
2014-02-10 18:40 ` bug#16717: Dumping: Can't update subspace record Paul Eggert
2014-02-13 14:39   ` Klaus Zeitler
2014-02-13 19:43     ` Paul Eggert
2014-02-13 19:54       ` Glenn Morris
2014-02-13 19:56         ` Glenn Morris
2014-02-13 20:32           ` Eli Zaretskii
2014-02-14  8:31           ` Paul Eggert
2014-02-14  1:45       ` Stefan Monnier
2014-02-10 18:33         ` Paul Eggert
2014-02-14  7:51           ` Glenn Morris
2014-02-14 17:31             ` Stefan Monnier [this message]
2014-02-14 14:42       ` Klaus Zeitler
2014-02-14 15:49         ` Paul Eggert

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=jwv7g8xob7t.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=16717@debbugs.gnu.org \
    --cc=Klaus.Zeitler@alcatel-lucent.com \
    --cc=eggert@cs.ucla.edu \
    --cc=rgm@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 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).