From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Is the autogen directory still needed?
Date: Mon, 28 Oct 2013 17:26:27 -0400 [thread overview]
Message-ID: <g1fvrlhyt8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83ppqrfjwk.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Oct 2013 05:54:35 +0200")
Eli Zaretskii wrote:
> I'm not interested in another "can we do something to make the MS-DOS
> port suffer" discussion.
Neither am I (I never have been).
I'm just saying, that _if_ the only justification we can come up with
for the existence of the autogen/ directory is that one developer needs
a few of the files within it from time-to-time for personal use, then
IMO that's not worth keeping in the repository and updating on a
(potentially) daily basis.
(Does bzr itself even run under MS-DOS, or do you fetch the sources in
some other OS, then transfer them across to a DOS environment? If so, or
even if not, just run autogen.sh in that other OS before you switch to
DOS.)
But maybe someone else will come up with a good reason why autogen/
should continue to exist, in which case the above is irrelevant.
next prev parent reply other threads:[~2013-10-28 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 19:12 Is the autogen directory still needed? Glenn Morris
2013-10-26 19:17 ` Paul Eggert
2013-10-26 19:59 ` Eli Zaretskii
2013-10-27 2:08 ` Glenn Morris
2013-10-27 2:11 ` Glenn Morris
2013-10-27 3:54 ` Eli Zaretskii
2013-10-28 21:26 ` Glenn Morris [this message]
2013-10-29 3:41 ` Eli Zaretskii
2013-10-29 13:44 ` Stefan Monnier
2013-11-05 8:00 ` Glenn Morris
2013-11-05 8:06 ` Glenn Morris
2013-11-05 16:12 ` Eli Zaretskii
2013-11-20 13:53 ` Xue Fuqiao
2013-10-27 2:57 ` Bruce Korb
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=g1fvrlhyt8.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--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).