From: Tim Cross <theophilusx@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: david.reitter@gmail.com,
Daniel Colascione <dan.colascione@gmail.com>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: New build process?
Date: Wed, 27 Jul 2011 18:31:25 +1000 [thread overview]
Message-ID: <CAC=50j8+7rBF0XfOwg9ocwtR=47eOL6bhBRPZjyWz8zZrw-dEA@mail.gmail.com> (raw)
In-Reply-To: <m3oc0ggmkc.fsf@hase.home>
On Wed, Jul 27, 2011 at 6:22 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Tim Cross <theophilusx@gmail.com> writes:
>
>> On Wed, Jul 27, 2011 at 6:07 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>>> Tim Cross <theophilusx@gmail.com> writes:
>>>
>>>> a typo - their quite common you know. Context usually helps to
>>>> recognize them. In this case, autogen is probably the most likely
>>>> candidate :)
>>>
>>> What has autogen to do with emacs?
>>>
>>
>> autogen.sh then if you must be pedantic about it,
>
> You wrote: "Previously, you ran autoget and now you run ./autogen.sh"
> (with typo fixed), now you claim: "Previously, you ran autogen.sh and
> now you run ./autogen.sh".
>
> That does not make sense to me.
You left no context before, so I had no idea what you were getting at.
As you will see in my reply to Eli, I was mistaken in my recollection.
However, now you have provided the context rather than just a word, I
can say that autoget should have been autoconf.
Tim
next prev parent reply other threads:[~2011-07-27 8:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 18:42 New build process? Alan Mackenzie
2011-07-26 18:47 ` David Kastrup
2011-07-26 20:00 ` David Reitter
2011-07-26 20:16 ` Daniel Colascione
2011-07-27 2:58 ` Richard Stallman
2011-07-27 3:40 ` Tim Cross
2011-07-27 5:08 ` Eli Zaretskii
2011-07-27 7:58 ` Tim Cross
2011-07-27 8:25 ` Peter Münster
2011-07-27 8:48 ` Tim Cross
2011-07-27 9:43 ` Peter Münster
2011-07-27 8:51 ` David Kastrup
2011-07-27 10:05 ` Eli Zaretskii
2011-07-27 10:03 ` Eli Zaretskii
2011-07-27 13:11 ` Tim Cross
2011-07-27 13:31 ` Lennart Borgman
2011-07-27 13:56 ` David Kastrup
2011-07-28 12:37 ` David De La Harpe Golden
2011-07-28 12:46 ` David Kastrup
2011-07-29 12:36 ` Alan Mackenzie
2011-07-27 14:58 ` Tim Cross
2011-07-27 16:14 ` Richard Stallman
2011-07-27 16:25 ` Eli Zaretskii
2011-07-27 20:27 ` Paul Eggert
2011-07-28 10:06 ` Eli Zaretskii
2011-07-28 16:45 ` Richard Stallman
2011-07-27 7:51 ` Andreas Schwab
2011-07-27 8:02 ` Tim Cross
2011-07-27 8:07 ` Andreas Schwab
2011-07-27 8:13 ` Tim Cross
2011-07-27 8:22 ` Andreas Schwab
2011-07-27 8:31 ` Tim Cross [this message]
2011-07-27 8:54 ` David Kastrup
2011-07-27 9:01 ` Andreas Schwab
2011-07-27 9:15 ` David Kastrup
2011-07-27 9:41 ` Andreas Schwab
2011-07-26 20:24 ` David Kastrup
2011-07-26 22:10 ` Alan Mackenzie
2011-07-27 12:15 ` Thien-Thi Nguyen
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='CAC=50j8+7rBF0XfOwg9ocwtR=47eOL6bhBRPZjyWz8zZrw-dEA@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=dan.colascione@gmail.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).