From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16465 invoked by alias); 14 Sep 2009 18:25:48 -0000 Received: (qmail 16445 invoked by uid 22791); 14 Sep 2009 18:25:46 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 Sep 2009 18:25:43 +0000 Received: (qmail 1530 invoked from network); 14 Sep 2009 18:25:41 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 14 Sep 2009 18:25:41 -0000 From: Pedro Alves To: gdb-patches@sourceware.org, Tom Tromey Subject: Re: Build question Date: Mon, 14 Sep 2009 18:25:00 -0000 User-Agent: KMail/1.9.10 Cc: danny.backx@scarlet.be, Eli Zaretskii References: <1250803105.11282.96.camel@pavilion> <1252834313.8804.51.camel@pavilion> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909141925.45707.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00434.txt.bz2 A Monday 14 September 2009 19:03:30, Tom Tromey escreveu: > >>>>> "Danny" == Danny Backx writes: > > Danny> Who are the libiberty maintainers ? Is this part of another GNU > Danny> project ? > > It is part of src but also part of gcc. > The maintainers are mentioned in gcc's MAINTAINERS file: > > libiberty DJ Delorie dj@redhat.com > libiberty Ian Lance Taylor ian@airs.com > > Tom > For completeness: you'd easilly know to look at gcc's MAINTAINERS file by first looking at the top level src/MAINTAINERS file: intl/; config.rhost; libiberty/; libiberty's part of include/ gcc: http://gcc.gnu.org Changes need to be done in tandem with the official GCC sources or submitted to the master file maintainer and brought in via a merge. Note: approved patches in gcc's libiberty or intl are automatically approved in this libiberty and intl also; feel free to merge them yourself if needed sooner than the next merge. Otherwise, changes are automatically merged, usually within a day. -- Pedro Alves