From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4812 invoked by alias); 14 Jul 2004 17:00:05 -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 4800 invoked from network); 14 Jul 2004 17:00:04 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 14 Jul 2004 17:00:04 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i6EH04e3026564 for ; Wed, 14 Jul 2004 13:00:04 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i6EH03016023; Wed, 14 Jul 2004 13:00:04 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id EEC3E2B9D; Wed, 14 Jul 2004 12:59:48 -0400 (EDT) Message-ID: <40F56684.9040906@gnu.org> Date: Wed, 14 Jul 2004 17:00:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Randolph Chung Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/committed] Mention hppa-linux in NEWS References: <20040629161506.GF28124@tausq.org> In-Reply-To: <20040629161506.GF28124@tausq.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00163.txt.bz2 > Any opinions/comments on bringing hppa out of "Maintainence only" mode? > I'm not exactly sure what that means/implies :) Not much, from further down: > All developers recognized by this file can make arbitrary changes to > OBSOLETE targets. > > All maintainers can test and thence approve non-trivial changes to > ``maintenance only'' targets submitted by recognized developers. > > All recognized developers can make mechanical changes (by virtue of > the obvious fix rule) to ``maintenance only'' targets. The change > shall be sanity checked by compiling with one of the listed targets. the tag to worry about is ``(broken)'' and that was removed some time ago. Andrew