From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Zaretskii Eli <ezaretski@elta.co.il>,
Daniel Jacobowitz <drow@mvista.com>,
Elena Zannoni <ezannoni@redhat.com>,
gdb@sources.redhat.com
Subject: Re: [maint] The GDB maintenance process
Date: Thu, 20 Feb 2003 16:19:00 -0000 [thread overview]
Message-ID: <3E55011F.8090801@redhat.com> (raw)
In-Reply-To: <53C2C20C-44E6-11D7-BE9F-000393575BCC@dberlin.org>
Daniel Berlin,
You and your track record are a case in point for why it is important to
for GDB developers to both receive and respect peer review. I find it
extreamly ironic that you, of all people, should be arguing that the
system is stifling.
Yes, the system was a barrier to you but that was for a very good
reason. Please don't try to use yourself as the sob story. The only
real mistake in your case was to not step in earlier and see you given
the boot.
Andrew
next prev parent reply other threads:[~2003-02-20 16:19 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 20:11 Zaretskii Eli
2003-02-20 14:58 ` Daniel Jacobowitz
2003-02-20 15:56 ` Andrew Cagney
2003-02-20 16:39 ` Andrew Cagney
2003-02-20 15:16 ` Daniel Berlin
2003-02-20 16:19 ` Andrew Cagney [this message]
2003-02-20 16:24 ` Daniel Berlin
2003-02-20 16:31 ` Daniel Berlin
2003-02-20 17:13 ` Daniel Berlin
2003-02-22 23:25 ` Eli Zaretskii
2003-02-23 1:57 ` Daniel Berlin
2003-02-23 19:23 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 5:29 Michael Elizabeth Chastain
2003-02-20 20:11 Zaretskii Eli
2003-02-18 6:08 Zaretskii Eli
2003-02-17 18:07 Daniel Jacobowitz
[not found] ` <drow@mvista.com>
2003-02-17 18:58 ` Kevin Buettner
2003-02-17 21:01 ` Elena Zannoni
2003-02-19 1:49 ` Daniel Jacobowitz
2003-02-19 2:26 ` Joel Brobecker
2003-02-19 15:43 ` Andrew Cagney
2003-02-19 16:29 ` Daniel Jacobowitz
2003-02-19 22:04 ` Andrew Cagney
2003-02-19 13:24 ` Daniel Berlin
2003-02-19 15:51 ` Andrew Cagney
2003-02-19 14:50 ` Andrew Cagney
2003-02-19 17:33 ` David Carlton
2003-02-19 17:57 ` Kevin Buettner
2003-02-19 18:56 ` Andrew Cagney
2003-02-19 20:39 ` Christopher Faylor
2003-02-19 23:17 ` Jason Molenda
2003-02-20 1:53 ` Christopher Faylor
2003-02-19 19:35 ` David Carlton
2003-02-20 18:32 ` Richard Earnshaw
2003-02-22 0:53 ` Andrew Cagney
2003-02-19 15:12 ` Andrew Cagney
2003-02-19 15:21 ` Daniel Jacobowitz
2003-02-19 16:24 ` Andrew Cagney
2003-02-19 18:36 ` Christopher Faylor
2003-02-19 23:36 ` Jason Molenda
2003-02-19 23:52 ` Andrew Cagney
2003-02-19 23:59 ` Jason Molenda
2003-02-20 0:16 ` Elena Zannoni
2003-02-20 0:21 ` Andrew Cagney
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 4:28 ` Andrew Cagney
2003-02-19 3:49 ` Jim Blandy
2003-02-19 16:14 ` Andrew Cagney
2003-02-19 16:31 ` Daniel Jacobowitz
2003-02-19 2:24 ` Jim Blandy
2003-02-19 16:33 ` Andrew Cagney
2003-02-19 22:24 ` Jim Blandy
2003-02-19 22:39 ` Christopher Faylor
2003-02-19 22:53 ` Andrew Cagney
2003-02-19 23:53 ` Elena Zannoni
2003-02-20 1:27 ` Andrew Cagney
2003-02-20 2:48 ` Andrew Cagney
2003-02-21 23:43 ` Andrew Cagney
2003-02-21 23:57 ` Andrew Cagney
2003-02-19 6:05 ` David Carlton
2003-02-23 23:26 ` Mark Kettenis
2003-02-24 7:18 ` 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=3E55011F.8090801@redhat.com \
--to=ac131313@redhat.com \
--cc=dberlin@dberlin.org \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=ezaretski@elta.co.il \
--cc=gdb@sources.redhat.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