From: Andrew Cagney <ac131313@redhat.com>
To: Stan Shebs <shebs@apple.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb@sources.redhat.com
Subject: Re: Features vs infrastructure (was Re: Tracepoint support in Cygnus GDB ?)
Date: Thu, 02 Oct 2003 05:31:00 -0000 [thread overview]
Message-ID: <3F7BB81C.6090403@redhat.com> (raw)
In-Reply-To: <3F7B9FEF.6070600@apple.com>
> Andrew Cagney wrote:
>
> Heh, I've been trolled! :-) I must say, I've been a little envious
> watching GDB development over the past couple of years; Cygnus was never
> able to afford so many cycles spent on internals. For multi-arch alone
> it took over three years from initial proposal to the actual hacking...
...
> You sound dubious... But in 1995 I drew up a document listing a bunch
> of directions for Cygnus to pursue with GDB, presented them at every
> quarterly meeting, and management would smile and nod and not make
> any promises. Multi-arch even got onto the future work schedule
> a couple times, but then contracts came in and bumped it off again.
> The 1995 doc is presumably still officially RH confidential, but
> perhaps you could get somebody over there to approve posting it; it
> would be a useful window into a less-well-known era of GDB history.
Do you accept that, in hindsite, such an approach was doomed to failure?
Mgt could never buy into such large infrastructure investments and,
hence, were paying you lip service. Even when you did get multi-arch
onto the scheduled, the work got cut short. multi-arch continues to be
finished by other means.
Rather than looking at features and infrastructure as adversaries, think
of them as mutual friends. One works off the other. A simplification
of the code here, leads to a simpler/faster/correct implementation of a
feature there.
During that period, Cygnus failed to recognize such benefits, and as a
consequence, swandered an oportunity to do infrastructure work for free.
Fortunatly, that has since changed.
Andrew
next prev parent reply other threads:[~2003-10-02 5:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 10:40 Tracepoint support in Cygnus GDB ? Saravanan
2003-09-24 18:12 ` Eli Zaretskii
2003-09-24 22:41 ` Jim Blandy
2003-09-25 4:02 ` Daniel Jacobowitz
2003-09-25 21:44 ` Andrew Cagney
2003-09-27 15:46 ` Eli Zaretskii
2003-09-27 17:49 ` Andrew Cagney
2003-09-27 18:37 ` Eli Zaretskii
2003-09-27 18:48 ` Andrew Cagney
2003-09-28 8:40 ` Eli Zaretskii
2003-09-28 19:44 ` Andrew Cagney
2003-09-28 21:07 ` Eli Zaretskii
2003-09-28 21:30 ` Daniel Jacobowitz
2003-09-29 5:36 ` Eli Zaretskii
2003-09-29 14:48 ` Daniel Jacobowitz
2003-09-28 22:25 ` Andrew Cagney
2003-09-29 5:41 ` Eli Zaretskii
2003-09-29 14:52 ` Andrew Cagney
2003-09-29 15:07 ` Daniel Jacobowitz
2003-10-01 21:49 ` Features vs infrastructure (was Re: Tracepoint support in Cygnus GDB ?) Stan Shebs
2003-10-02 3:29 ` Andrew Cagney
2003-10-02 3:47 ` Stan Shebs
2003-10-02 5:31 ` Andrew Cagney [this message]
2003-10-02 6:42 ` Stan Shebs
2003-10-02 7:02 ` Joel Brobecker
2003-10-02 19:18 ` Andrew Cagney
2003-10-02 6:04 ` Stan Shebs
2003-10-02 6:29 ` Andrew Cagney
2003-09-30 5:43 ` Tracepoint support in Cygnus GDB ? Jim Blandy
2003-09-30 21:14 ` Andrew Cagney
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=3F7BB81C.6090403@redhat.com \
--to=ac131313@redhat.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=shebs@apple.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