From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: what make-dist should include [was Re: Emacs pretest 26.1.91 is out]
Date: Wed, 16 Jan 2019 05:30:50 -0500 [thread overview]
Message-ID: <7zfttsgahx.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <4745c966-4531-f946-8eca-de996c3958d2@cs.ucla.edu> (Paul Eggert's message of "Thu, 10 Jan 2019 18:31:14 -0800")
Paul Eggert wrote:
> On 1/10/19 5:03 PM, Glenn Morris wrote:
>> The current philosophy is "omit things that aren't relevant".
>
> Sure, but the question is "What's relevant?" and the answer depends on
> the audience. For example, .gitignore is relevant to anybody who
> checks a tarball's files into a fresh Git repository,
(and then builds in place)
> and msdos/autogen is relevant to anybody who does serious development
> on MS-DOS regardless of whether they're using Git.
I doubt such people exist, for either example.
I see zero practical advantages to a switch to a "distribute everything"
approach (which Emacs has never done, and nor when I check do eg tar,
texinfo, coreutils); unless it will drastically simplify make-dist and
avoid problems like the one fixed in 021f34b. If it does then I am all
for it. :)
next prev parent reply other threads:[~2019-01-16 10:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 16:10 Emacs pretest 26.1.91 is out Nicolas Petton
2019-01-07 21:42 ` John Wiegley
2019-01-07 22:11 ` Glenn Morris
2019-01-07 23:03 ` Nicolas Petton
2019-01-08 3:35 ` Eli Zaretskii
2019-01-08 0:59 ` Paul Eggert
2019-01-11 1:03 ` Glenn Morris
2019-01-11 2:31 ` Paul Eggert
2019-01-16 10:30 ` Glenn Morris [this message]
2019-01-17 5:42 ` what make-dist should include [was Re: Emacs pretest 26.1.91 is out] Mike Kupfer
2019-01-17 21:44 ` Stefan Monnier
2019-01-18 0:18 ` Mike Kupfer
2019-01-18 3:01 ` Stefan Monnier
2019-01-20 1:08 ` Mike Kupfer
2019-01-20 14:42 ` Stefan Monnier
2019-01-18 8:38 ` Eli Zaretskii
2019-01-20 0:54 ` Mike Kupfer
2019-01-18 18:58 ` Glenn Morris
2019-01-22 21:58 ` Paul Eggert
2019-01-23 16:14 ` Eli Zaretskii
2019-01-23 17:52 ` Paul Eggert
2019-01-23 18:14 ` Eli Zaretskii
2019-01-08 1:25 ` Emacs pretest 26.1.91 is out Paul Eggert
2019-01-08 8:53 ` Nicolas Petton
2019-01-09 15:02 ` Phillip Lord
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=7zfttsgahx.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).