From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31919 invoked by alias); 7 Feb 2011 15:35:54 -0000 Received: (qmail 31833 invoked by uid 22791); 7 Feb 2011 15:35:53 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 07 Feb 2011 15:35:48 +0000 Received: (qmail 15397 invoked from network); 7 Feb 2011 15:35:47 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 7 Feb 2011 15:35:47 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [PATCH] libdecnumber: start a gitignore Date: Mon, 07 Feb 2011 15:35:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.5.1; x86_64; ; ) Cc: Mike Frysinger , Tom Tromey , toolchain-devel@blackfin.uclinux.org References: <1297059100-13432-1-git-send-email-vapier__34363.9684761458$1297059122$gmane$org@gentoo.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201102071535.44195.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: 2011-02/txt/msg00159.txt.bz2 On Monday 07 February 2011 15:18:51, Mike Frysinger wrote: > > Mike> libdecnumber/.gitignore | 1 + > > > > I think this has to go to gcc-patches. > > np ... i couldnt find info that indicated where to send stuff for this subdir FYI, it's in the top-level src/MAINTAINERS: libdecnumber/ See libiberty. The master copy of this directory is in the GCC repository. ... 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