Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Lord <lord@emf.net>
To: aj@suse.de
Cc: neil@daikokuya.demon.co.uk, rth@redhat.com,
	zack@codesourcery.com, jimb@redhat.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com
Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
Date: Tue, 26 Mar 2002 22:54:00 -0000	[thread overview]
Message-ID: <200203270654.WAA29550@emf.net> (raw)
In-Reply-To: <u8n0wupl8q.fsf@gromit.moeb> (message from Andreas Jaeger on Wed, 27 Mar 2002 07:39:49 +0100)



       Further enhancing the testing infrastructure is one objective that I'd
       like to see and where I've worked on already,

Yes.  The GCC project has _very_noticably_ improved in many process
areas since roughly the time the SC came on-line.

I come from a very "software tools" oriented background.  I think
there's a lot of leverage to be obtained not by waiting for volunteers
to contribute things that happen to be useful, but by making an
aggressive, worked-out plan and then asking how it can be implemented
via funded projects.  The SC mission statement contains lofty goals,
but it isn't an aggressive, actionable plan for the most part.  The
list discussions contain many good ideas and initiatives, but overall,
that's a scattershot rather than an especially organized approach to
the problem.

And it's an issue that's both larger than GCC, but to which GCC can
make a very useful contribution.  Well designed tools for improving
the GCC process will work for other projects as well.  At the same
time, GCC, more than most projects, exemplifies both the strengths and
challenges of open source processes -- an emerging software
engineering discipline of exponentially increasing commercial and
social importance.

-t


  reply	other threads:[~2002-03-27  6:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 15:40 sharing libcpp between GDB and GCC Jim Blandy
2002-03-25 20:07 ` Zack Weinberg
2002-03-25 23:18   ` Neil Booth
2002-03-26 14:29   ` gcc development schedule [Re: sharing libcpp between GDB and GCC] Richard Henderson
2002-03-26 14:37     ` David Edelsohn
2002-03-26 21:32       ` Andreas Jaeger
2002-03-26 15:17     ` Neil Booth
2002-03-26 15:30       ` Tom Lord
2002-03-26 15:40         ` David Edelsohn
2002-03-26 16:03           ` Tom Lord
2002-03-26 16:41             ` Tim Hollebeek
2002-03-26 22:23               ` Eli Zaretskii
2002-03-26 22:43                 ` Tom Lord
2002-03-27  7:18                   ` mike stump
2002-03-27  9:00                     ` law
2002-03-27 10:13                       ` Neil Booth
2002-03-26 22:45                 ` Tom Lord
2002-03-26 23:11                 ` Daniel Berlin
2002-03-26 23:53                   ` Tom Lord
2002-03-27  4:32                     ` Fergus Henderson
2002-03-27  6:30                     ` Andrew Cagney
2002-03-27  6:43                       ` Gianni Mariani
2002-03-26 22:39         ` Andreas Jaeger
2002-03-26 22:54           ` Tom Lord [this message]
2002-03-26 15:31       ` Zack Weinberg
2002-03-27  6:01 Robert Dewar
2002-03-27 19:17 Kaveh R. Ghazi
2002-03-27 19:46 ` Zack Weinberg
2002-03-28  1:24   ` Gerald Pfeifer
2002-03-28  1:53     ` Jason Molenda
2002-03-28  2:01       ` Jason Molenda
2002-03-28  7:17         ` Christopher Faylor
2002-03-28  9:01       ` David O'Brien
2002-03-28 21:29         ` Christopher Faylor
2002-03-28  9:00     ` David O'Brien
2002-04-03 14:19   ` Jim Blandy
2002-04-03 14:29     ` Phil Edwards
2002-03-28 12:34 ` Phil Edwards

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=200203270654.WAA29550@emf.net \
    --to=lord@emf.net \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=rth@redhat.com \
    --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