From: fche@redhat.com (Frank Ch. Eigler)
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb-patches@sources.redhat.com, fche@redhat.com
Subject: Re: Stepping down from several maintainership roles
Date: Tue, 18 Mar 2003 19:16:00 -0000 [thread overview]
Message-ID: <o5isugwkm3.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <3E75E30D.90803@redhat.com>
fnasser wrote:
> My new responsibilities in my job and the project I am working on
> are not allowing me to be responsive to the list requests. This will
> remain like that until the end of the Summer. [...] So I am
> stepping down from several maintainership roles. [...]
This is too bad. It appears that in order to solve the problem of
insufficient time availability of maintainers, several of them have
been nagged in order to get them to resign. These people having
history and experience have been pressured into severing ties
outright, making it likely that they spend even less time on gdb. How
is this supposed to be progress?
- FChE
next prev parent reply other threads:[~2003-03-18 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 14:59 Fernando Nasser
2003-03-18 19:16 ` Frank Ch. Eigler [this message]
2003-03-21 20:20 ` David Carlton
2003-03-21 22:34 ` 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=o5isugwkm3.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@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