From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5262 invoked by alias); 23 Aug 2011 22:06:16 -0000 Received: (qmail 5253 invoked by uid 22791); 23 Aug 2011 22:06:15 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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; Tue, 23 Aug 2011 22:05:55 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p7NM5sYj023574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Aug 2011 18:05:54 -0400 Received: from psique ([10.3.112.13]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p7NM5lhm004711; Tue, 23 Aug 2011 18:05:50 -0400 From: Sergio Durigan Junior To: Josh Matthews Cc: Jan Kratochvil , gdb-patches@sourceware.org Subject: Re: [PATCH] Fix darwin build error References: <20110823194241.GA31319@host1.jankratochvil.net> Date: Tue, 23 Aug 2011 22:06:00 -0000 In-Reply-To: (Josh Matthews's message of "Tue, 23 Aug 2011 16:47:01 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-08/txt/msg00429.txt.bz2 Hi Josh, Josh Matthews writes: > Thanks very much everybody. I couldn't find any good guideline for how > to format the email (and especially the changelot entry) so I cribbed > off of a random email that was sent recently. It would be quite > helpful if someone could put together a webpage that listed Ok, you did good, thanks for the patch. > 1) what you do with a patch you've written (attach to a bug tracker? > send to the list?) > 2) how to format the email As Jan already mentioned, you can find most of this information in gdb/CONTRIBUTE. Note that we also follow coding standards (Jan already mentioned that, too). > 3) how to do stuff related to copyright assignment There is an entry abou this on gdb/CONTRIBUTE as well. I may be wrong here, but in my understanding we take care of this issue only when the person submits the patch (as you did). I will forward the procedure to you. Thanks, Sergio.