Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: Tracepoint support in Cygnus GDB ?
Date: Mon, 29 Sep 2003 06:28:00 -0000	[thread overview]
Message-ID: <uy8w8gko5.fsf@elta.co.il> (raw)
In-Reply-To: <200309282245.h8SMjhoO026916@duracef.shout.net> (message from Michael Elizabeth Chastain on Sun, 28 Sep 2003 18:45:43 -0400)

> Date: Sun, 28 Sep 2003 18:45:43 -0400
> From: Michael Elizabeth Chastain <mec@shout.net>
> 
> You can control directly the maintainer resources that you contribute.
> If someone is listed as a maintainer you can ask them to perform the
> functions of their maintainership (review your patches).  You can nag
> people, or inspire people, to do things that you think are important.
> But we don't take orders from a centralized leader.

I agree (how could I disagree? how could someone who've read my
messages think I'd disagree?).  I don't think my messages in this
discussion were trying to do anything but ask, inspire and perhaps
nag.

However, there's something called leadership that, if applied with the
kind of wisdom that I so cherish in the GDB maintenance team, tends to
guide the troops even if there are no orders and no centralized
control.

If the leaders state specific goals, and do that convincingly, the
other contributors will most probably follow suit.  At least that's
my experience.

> I self-generated these goals.  I'm open to input on them, but basically,
> you would have a hard time convincing me to change my overall philosophy
> from my vision (QA) to your vision (user-level features).

I hope you will agree that a program exists to provide user-level
features, not to satisfy QA.  QA is a means; I hope there's ends to
which the means exists.


  reply	other threads:[~2003-09-29  5:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 22:50 Michael Elizabeth Chastain
2003-09-29  6:28 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-29 13:21 Michael Elizabeth Chastain
2003-09-24 10:40 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-09-30  5:43           ` 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=uy8w8gko5.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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