|
From: | Andrew Cagney |
Subject: | Re: [Gdbheads] Steering Committee nominations |
Date: | Tue, 24 Feb 2004 14:05:59 -0500 |
User-agent: | Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.4.1) Gecko/20040217 |
Andrew Cagney <address@hidden> writes:
For area and core developers, not subscribed to gdb@ and gdb-patches@ would be one clear trigger.
The key word here is "trigger", and the key question "subscribed to gdb@ and gdb-patches@". How the trigger is resolved is obviously a separate problem.
A lead or core developer that is not subscribed to those lists is in no position to carry out their responsibilities (such as patch review) diligently.
Consequently, we assume that lead and core developers are subscribed to the gdb@ and gdb-patches@ lists, and must treat any situation where a developer has intentionally unsubscribed with at least a certain degree of suspicion.
It might be useful to check the subscription lists and table the results. Andrew
[Prev in Thread] | Current Thread | [Next in Thread] |