From: Paul Eggert <eggert@CS.UCLA.EDU>
To: "Zack Weinberg" <zack@codesourcery.com>
Cc: Ben Elliston <bje@wasabisystems.com>,
gcc@gcc.gnu.org, binutils@sources.redhat.com,
gdb@sources.redhat.com, rms@gnu.org
Subject: Re: flag day for Solaris portions of config.{guess,sub}
Date: Sat, 29 Nov 2003 01:42:00 -0000 [thread overview]
Message-ID: <871xrs5b9j.fsf@penguin.cs.ucla.edu> (raw)
In-Reply-To: <87wu9mt79r.fsf@egil.codesourcery.com>
"Zack Weinberg" <zack@codesourcery.com> writes:
> THE OUTPUT OF CONFIG.GUESS MUST NOT EVER CHANGE.
> EVEN IF IT IS WRONG.
It isn't reasonable to insist on this as an absolute policy. If this
policy were strictly adhered to, most of the changes to config.guess
would be disallowed, as config.guess typically outputs something wrong
on unusual hosts.
People make mistakes. Systems change. The output of config.guess has
changed in the past, and it will change in the future. The very name
"config.guess" suggests that its output should not be considered to be
unchanging truth.
next prev parent reply other threads:[~2003-11-28 23:22 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 12:25 Ben Elliston
2003-11-20 14:03 ` Ben Elliston
2003-11-20 14:12 ` Eric Botcazou
2003-11-20 18:29 ` Rainer Orth
2003-11-20 20:31 ` Paul Eggert
2003-11-20 20:35 ` Rainer Orth
2003-11-20 20:50 ` Albert Chin-A-Young
2003-11-20 21:32 ` Paul Eggert
2003-11-20 21:44 ` Rainer Orth
2003-11-21 0:57 ` Paul Eggert
2003-11-21 1:15 ` Rainer Orth
2003-11-23 12:51 ` Richard Stallman
2003-11-23 23:40 ` Branko Čibej
2003-11-24 8:17 ` Paul Eggert
2003-11-24 8:28 ` Eric Botcazou
2003-11-24 12:08 ` Paul Eggert
2003-11-24 14:35 ` Eric Botcazou
2003-11-24 21:54 ` Paul Eggert
2003-11-25 10:47 ` Eric Botcazou
2003-11-25 23:12 ` Paul Eggert
2003-11-26 6:05 ` Eric Botcazou
2003-11-26 12:05 ` Ben Elliston
2003-11-27 1:58 ` Russ Allbery
2003-11-25 10:07 ` Richard Stallman
2003-11-26 3:49 ` Zack Weinberg
2003-11-20 21:33 ` Eric Botcazou
2003-11-20 21:40 ` Rainer Orth
2003-11-20 23:32 ` Phil Edwards
2003-11-21 23:56 ` tm_gccmail
2003-11-22 0:01 ` Joe Buck
2003-11-27 18:55 ` Zack Weinberg
2003-11-29 1:42 ` Paul Eggert [this message]
2003-11-29 2:24 ` Zack Weinberg
2003-12-01 21:29 ` Paul Eggert
2003-12-01 22:09 ` Zack Weinberg
2003-12-02 21:40 ` Paul Eggert
2003-12-02 21:45 ` Zack Weinberg
2003-12-02 22:21 ` Ben Elliston
2003-12-03 17:22 ` Richard Stallman
2003-12-03 17:23 ` Zack Weinberg
2003-12-03 17:33 ` Arnaud Charlet
2003-12-04 7:42 ` Richard Stallman
2003-12-04 8:57 ` Branko Čibej
2003-12-05 17:27 ` Richard Stallman
2003-12-05 18:43 ` Zack Weinberg
2003-12-05 18:53 ` Joe Buck
2003-12-06 12:11 ` Nix
2003-12-07 23:22 ` Branko Čibej
2003-12-04 10:16 ` Zack Weinberg
2003-12-04 11:16 ` Ben Elliston
2003-12-04 21:41 ` Paul Eggert
2003-12-04 22:07 ` Zack Weinberg
2003-12-04 23:04 ` Arnaud Charlet
2003-12-04 23:11 ` Alexandre Oliva
2003-12-04 23:27 ` Joe Buck
2003-12-04 23:38 ` Zack Weinberg
2003-12-04 23:41 ` Ben Elliston
2003-12-04 23:42 ` Zack Weinberg
2003-12-05 11:46 ` Alexandre Oliva
2003-12-06 7:05 ` Eric Botcazou
2003-12-06 20:41 ` Alexandre Oliva
2003-12-06 21:56 ` Eric Botcazou
2003-12-07 9:25 ` Arnaud Charlet
2003-12-07 15:26 ` Eric Botcazou
2003-12-07 19:25 ` Zack Weinberg
2003-12-05 5:00 ` Russ Allbery
2003-12-05 12:37 ` Alexandre Oliva
2003-12-08 13:29 ` Rainer Orth
2003-12-08 22:44 ` Paul Eggert
2003-12-08 23:48 ` Rainer Orth
2003-12-08 23:59 ` Zack Weinberg
2003-12-10 0:04 ` Paul Eggert
2003-12-12 5:30 ` Alexandre Oliva
2003-12-12 7:19 ` Zack Weinberg
2003-12-12 21:27 ` Rainer Orth
2003-12-05 23:22 ` Richard Stallman
2003-12-04 14:22 ` Andrew Cagney
2003-11-20 21:55 bkorb
2003-11-20 23:24 ` Rainer Orth
2003-11-20 23:52 ` Bruce Korb
2003-12-02 22:58 Wolfgang Bangerth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871xrs5b9j.fsf@penguin.cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=binutils@sources.redhat.com \
--cc=bje@wasabisystems.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rms@gnu.org \
--cc=zack@codesourcery.com \
/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.
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).