From: DJ Delorie <dj@redhat.com>
To: mark@codesourcery.com
Cc: neroden@doctormoo.dyndns.org, gcc@gcc.gnu.org,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: configure/make/make install with moving srcdir, builddir...
Date: Thu, 04 Jul 2002 16:34:00 -0000 [thread overview]
Message-ID: <200207042332.g64NWt711432@greed.delorie.com> (raw)
In-Reply-To: <61310000.1025803091@warlock.codesourcery.com> (message from Mark Mitchell on Thu, 04 Jul 2002 10:18:11 -0700)
> In order to make progress, we know we can't make an incremental change;
> we need to make a drastic change. (In this case, autoconfiscation.) But,
> it's hard to do that and preserve every last feature of the old system,
> all at once. (For one thing, the compiler keeps changing as you go.)
I agree somewhat. IMHO it's important to at least think about all the
features, so we don't *inadvertently* disable one. But more important
is to think of what the users are trying to accomplish, and is there
some *other* way they could do that? If so, we have some flexibility
in how to move forward.
So, to me, it's better to say "What about XYZ?" "No, we're dropping
that" than to say "Oops! We forgot about XYZ" later. But better yet
to just support it if it's reasonable to do so.
prev parent reply other threads:[~2002-07-04 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 16:15 Nathanael Nerode
2002-07-04 0:19 ` Mark Mitchell
2002-07-04 9:36 ` DJ Delorie
2002-07-04 10:19 ` Mark Mitchell
2002-07-04 14:20 ` Geoff Keating
2002-07-05 9:45 ` Mark Mitchell
2002-07-04 16:34 ` DJ Delorie [this message]
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=200207042332.g64NWt711432@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mark@codesourcery.com \
--cc=neroden@doctormoo.dyndns.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox