From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22780 invoked by alias); 21 Feb 2013 20:26:47 -0000 Received: (qmail 22756 invoked by uid 22791); 21 Feb 2013 20:26:45 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Feb 2013 20:26:34 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r1LKQXan007115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Feb 2013 15:26:33 -0500 Received: from host2.jankratochvil.net (ovpn-116-18.ams2.redhat.com [10.36.116.18]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r1LKQTIR012752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 21 Feb 2013 15:26:32 -0500 Date: Thu, 21 Feb 2013 20:26:00 -0000 From: Jan Kratochvil To: gdb-patches@sourceware.org Subject: [patch] gdb/CONTRIBUTE update Message-ID: <20130221202629.GA30015@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) 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: 2013-02/txt/msg00570.txt.bz2 Hi Eli, there is one s/conclusion/inclusion/ fix reviewed by Phil. Otherwise TBH I did not well understand the "distribute the change yourself" encouragement, it seems to me like a suggestion one should keep 3rd party patches, these are discouraged, patches should be integrated to FSF GDB. And added the new paragraph as people send patch and as they expect the GDB maintainers will grab it and handle it on their own many patches get forgotten that way as there is no patch tracking in place (yet). Just such an idea, np if people consider it OK as is. Thanks, Jan gdb/ 2013-02-21 Jan Kratochvil * CONTRIBUTE: Fix type to inclusion. Extend patches distribution description. Add new paragraph on patch ownership. diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE index cdec246..67af0ab 100644 --- a/gdb/CONTRIBUTE +++ b/gdb/CONTRIBUTE @@ -10,8 +10,9 @@ included in the GDB distribution, the GDB web pages also contain much information. You may also want to submit your change so that can be considered for -conclusion in a future version of GDB (see below). Regardless, we -encourage you to distribute the change yourself. +inclusion in a future version of GDB (see below). Regardless, we +encourage you to distribute the change yourself until it gets integrated +into FSF GDB mainline sources. If you don't feel up to hacking GDB, there are still plenty of ways to help! You can answer questions on the mailing lists, write @@ -86,6 +87,12 @@ o Submitting Patches CVS repository, see the Anonymous read-only CVS access and Read-write CVS access page. + Patch from a contributor needs a review with approval from + maintainer. Still you drive the review process and inclusion + process of the patch. If there is no reply in a week send a new + mail (not reply) with PING in its subject. Occasionally even + a PING^2 mail may be needed in another week of no replise. + -- Supplemental information for GDB: