From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20380 invoked by alias); 8 Oct 2003 17:57:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20361 invoked from network); 8 Oct 2003 17:57:32 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 8 Oct 2003 17:57:32 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 865062B89; Wed, 8 Oct 2003 13:57:30 -0400 (EDT) Message-ID: <3F84500A.30405@redhat.com> Date: Wed, 08 Oct 2003 17:57:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Snyder Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com, kettenis@gnu.org Subject: Re: RFC: patch to lin-lwp.c References: <3F303C1E.7040304@redhat.com> <3F3136AD.4010300@redhat.com> <20031004214120.GA24856@nevyn.them.org> <3F83582B.1060408@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00226.txt.bz2 >> If not, I'd like to clearly indicate who can approve patches > to lin-lwp.c. > > It's more who ought to than who can. I think any of you, me, > Mark, or Jim Blandy (and maybe we ought to add Jeff Johnston) > are qualified to approve them, but I don't know which one or > two persons understand it fully enough to be called on as a > maintainer. Jim and I, for instance, worked on it a long time > ago. > > Part of the problem, I think, is that nobody really wants it. > It's complicated, difficult, and fragile. The general trend for such code to not have an explicit maintainer. Instead changes get approved using peer-review that involves at least one core maintainer. Anything architectural being pulled out and discssed separatly. I should also red flag that changing the target vector means changing the thread code so "it could be fun times". enjoy, Andrew