From: Glenn Morris <rgm@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: make-dist failure on master
Date: Thu, 13 Jun 2019 11:55:09 -0400 [thread overview]
Message-ID: <vlef3x32g2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87o935izmx.fsf@russet.org.uk> (Phillip Lord's message of "Mon, 10 Jun 2019 10:00:06 +0100")
Phillip Lord wrote:
>> Sounds like a bug. (Though my, presumably outdated or wrong,
>> recollection was that make-dist required an in-tree build.)
>
> Effectively it does, unless you use the right options. Whether that was
> a design decision or not, I don't know.
Actually, maybe it was the ChangeLog needing an in-tree build that I was
thinking of.
IMO --snapshot should do whatever is appropriate to make an Emacs
tarfile for use on ftp.gnu.org. I think that includes sanity-checking
and adding a ChangeLog.
I don't have an opinion on whether make-dist needs to support
out-of-tree builds.
prev parent reply other threads:[~2019-06-13 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 20:38 make-dist failure on master Phillip Lord
2019-06-08 21:43 ` Paul Eggert
2019-06-08 22:49 ` Phillip Lord
2019-06-09 1:28 ` Paul Eggert
2019-06-09 1:46 ` Glenn Morris
2019-06-10 9:00 ` Phillip Lord
2019-06-13 15:55 ` Glenn Morris [this message]
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=vlef3x32g2.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--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).