From: Glenn Morris <rgm@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change to bzr build instructions
Date: Tue, 22 Mar 2011 23:15:58 -0400 [thread overview]
Message-ID: <2q39mey1ap.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m362rbqz55.fsf@linux-m68k.org> (Andreas Schwab's message of "Tue, 22 Mar 2011 10:32:06 +0100")
Andreas Schwab wrote:
> You should also remove all the other files that would be added by
> running autoreconf (config.{guess,sub}, depcomp, missing, etc.).
Awesome, I'll remove them in a few days if no-one objects; and make the
required changes to autogen.sh, autogen/, etc.
I think the list is:
compile config.guess config.sub depcomp install-sh missing
(technically could also do texinfo.tex, but I won't)
The only reason I can see to keep some or all of these files is if for
some reason Emacs has to have the very latest version (compared to what
automake 1.11 supplies).
next prev parent reply other threads:[~2011-03-23 3:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 0:24 Change to bzr build instructions Glenn Morris
2011-03-21 0:46 ` Glenn Morris
2011-03-21 16:06 ` Jim Meyering
2011-03-21 22:33 ` Stefan Monnier
2011-03-22 3:31 ` Glenn Morris
2011-03-22 5:42 ` Stefan Monnier
2011-03-22 7:16 ` Glenn Morris
2011-03-22 8:08 ` Jim Meyering
2011-03-22 9:32 ` Andreas Schwab
2011-03-23 3:15 ` Glenn Morris [this message]
2011-03-22 11:36 ` Andreas Röhler
2011-03-22 13:09 ` Harald Hanche-Olsen
2011-03-22 18:37 ` Glenn Morris
2011-03-25 9:54 ` Eli Zaretskii
2011-03-25 10:04 ` David Kastrup
2011-03-25 10:18 ` Eli Zaretskii
2011-03-25 11:44 ` Leo
2011-03-25 13:07 ` David Kastrup
2011-03-25 13:13 ` Eli Zaretskii
2011-03-25 13:52 ` David Kastrup
2011-03-25 16:02 ` Eli Zaretskii
2011-03-25 13:45 ` Andreas Röhler
2011-03-27 18:54 ` Davis Herring
2011-03-25 14:37 ` Ted Zlatanov
2011-03-25 15:03 ` David Kastrup
2011-03-25 15:16 ` Ted Zlatanov
2011-03-25 15:32 ` David Kastrup
2011-03-25 16:08 ` Eli Zaretskii
2011-03-25 19:55 ` Stefan Monnier
2011-03-28 1:11 ` Miles Bader
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=2q39mey1ap.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).