public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
	insight@sources.redhat.com, gcc-patches@gcc.gnu.org,
	dj@redhat.com
Subject: Re: [toplevel patch] delete references to tix
Date: Mon, 10 Mar 2003 19:14:00 -0000	[thread overview]
Message-ID: <oradg3hwii.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030310182220.GA461@doctormoo>

On Mar 10, 2003, Nathanael Nerode <neroden@twcny.rr.com> wrote:

> Insight ripped tix out of CVS.  Time to get rid of it I think.

Maybe it's a bit too early?  Consider that someone might create a
unified tree out of the latest stable releases of the tools, as
described in the CrossGCC FAQ IIRC, and then, if it turns out that the
insight release still uses tix, but the toplevel no longer does, we
lose.

I fail to see the point of removing stuff from the top-level just
because it appears to be unused.  The top-level tree is not just for
the tools, it was originally meant as a way to enable one to build a
number of projects in a single step.  Now it fails badly at that,
thanks to your `clean-ups' to ease the autoconfiscation.  Removing a
number of those projects has given us no benefit whatsoever, and
actually made the top-level less useful than it was.  I'm sure it
wouldn't have been that hard to keep a few additional host_modules,
even if they didn't appear to be used any more.

I wish you were *far* more conservative when considering whether to
remove something from the tree.  It's not like it's hard to put stuff
back in, but then we'll be going in circles.

Please defer the installation of this patch until a stable release of
gdb/insight is out there that no longer uses tix.  Ok to install 1-2
weeks afterwards.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  parent reply	other threads:[~2003-03-10 19:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 18:38 Nathanael Nerode
2003-03-10 19:07 ` Keith Seitz
2003-03-10 19:14 ` Alexandre Oliva [this message]
2003-03-10 19:19   ` Martin M. Hunt
2003-03-10 20:11     ` Alexandre Oliva
2003-03-10 21:54       ` Martin M. Hunt
2003-03-11  0:21         ` Andrew Cagney
2003-03-11  0:31           ` Alexandre Oliva
2003-03-11  0:38             ` Martin M. Hunt
2003-03-11  0:47             ` David Carlton
2003-03-11 14:10               ` Alexandre Oliva
2003-03-11 18:24               ` AW: " Carsten Schlote
2003-03-15  4:17 Nathanael Nerode

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=oradg3hwii.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=neroden@twcny.rr.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).