From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob@brasko.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb@sources.redhat.com, cagney@redhat.com, ezannoni@redhat.com,
fnasser@redhat.com
Subject: Re: patch review time
Date: Sat, 05 Mar 2005 20:34:00 -0000 [thread overview]
Message-ID: <16938.5992.336181.640228@farnswood.snap.net.nz> (raw)
> BTW, 2 of the MI MAINTAINERS completely do *nothing*. They don't respond
> to Emails, they don't review patches, and as far as I can tell, do
> nothing behind the scene.
> Shouldn't they be removed from this position, since, IMO, they are *not*
> maintaining the code. I think having 3 maintainers under the section
> mi (gdb/mi) Andrew Cagney cagney@redhat.com
> Elena Zannoni ezannoni@redhat.com
> Fernando Nasser fnasser@redhat.com
> is misleading. Since Andrew is the *only* one I can tell is maintaining
> code for MI, even if it's not at the speed that I desire.
Hang on. Let's be pragmatic. How will things get *better* if they are removed.
They are the original authors and know the code better than the rest of us.
We don't know what their committments/current interests are. At the moment,
they might contribute at some time in the future. If they are removed then
presumably they won't.
Bob, you're not the only one whose e-mails go ignored. Answering questions,
reviewing patches takes up time. Unpaid time. If my e-mail is unanswered, it
tells me something: either people aren't interested or they are too busy.
Sometimes I let it go, sometimes I realise it was a stupid question, and
sometimes I send another e-mail and try to add something to get a reply.
It only makes sense to remove people from MAINTAINERS if some-one else is
stepping forward with the enough expertise and enthusiasm. Right know,
with MI, AFAIK they aren't. Shit happens.
Nick
next reply other threads:[~2005-03-05 20:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 20:34 Nick Roberts [this message]
2005-03-05 22:06 ` Bob Rossi
2005-03-05 22:15 ` Kip Macy
2005-03-06 13:45 ` Bob Rossi
2005-03-06 15:57 ` Daniel Jacobowitz
2005-03-06 18:06 ` Bob Rossi
2005-03-06 0:11 ` Russell Shaw
2005-03-06 13:48 ` Bob Rossi
2005-03-06 18:50 ` Eli Zaretskii
2005-03-06 20:17 ` Daniel Berlin
2005-03-06 20:29 ` Bob Rossi
2005-03-07 4:38 ` Eli Zaretskii
2005-03-07 23:49 ` Bob Rossi
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 15:02 Bob Rossi
2005-03-04 7:35 ` Eli Zaretskii
2005-03-04 14:26 ` Bob Rossi
2005-03-04 14:59 ` Dave Korn
2005-03-04 15:36 ` 'Bob Rossi'
2005-03-04 15:43 ` Eli Zaretskii
2005-03-04 15:54 ` Bob Rossi
2005-03-04 17:39 ` Eli Zaretskii
2005-03-04 22:17 ` Bob Rossi
2005-03-05 11:28 ` Eli Zaretskii
2005-03-05 15:27 ` Bob Rossi
2005-03-05 17:13 ` Eli Zaretskii
2005-03-05 17:17 ` Kip Macy
2005-03-06 4:46 ` Eli Zaretskii
2005-03-06 6:24 ` Kip Macy
2005-03-06 18:54 ` Eli Zaretskii
2005-03-06 20:20 ` Bob Rossi
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=16938.5992.336181.640228@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=cagney@redhat.com \
--cc=eliz@gnu.org \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).