From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24156 invoked by alias); 12 May 2003 11:27:30 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 6793 invoked from network); 12 May 2003 11:24:12 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 12 May 2003 11:24:12 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4CBOCH28188 for ; Mon, 12 May 2003 07:24:12 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4CBOCI07463; Mon, 12 May 2003 07:24:12 -0400 Received: from localhost.localdomain.redhat.com (vpn50-19.rdu.redhat.com [172.16.50.19]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4CBO9800310; Mon, 12 May 2003 07:24:11 -0400 To: Salvador Eduardo Tropea Cc: binutils@sources.redhat.com Subject: Re: RFC objdump new feature to generate debug info using ctags style References: <3EB293A4.30103@inti.gov.ar> From: Nick Clifton Date: Mon, 12 May 2003 11:27:00 -0000 In-Reply-To: <3EB293A4.30103@inti.gov.ar> (Salvador Eduardo Tropea's message of "Fri, 02 May 2003 12:49:56 -0300") Message-ID: User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg00375.txt.bz2 Hi Salvador, > I managed to modify prdbg.c to print the information in a format > compatible with Exuberant Ctags (plus some fields not available in > E.Ctags). Thanks very much for submitting this patch. Since this patch adds a new feature to objdump it definitely needs a copyright assignment before it can be accepted. If you are willing to make such an assignment please fill out the email form attached below and send it off the FSF. The process will take a while but it should be worth it as they we can consider accepting your patches. As for the patch itself, there are a couple of issues: * It needs a ChangeLog entry. * Since you are adding a new feature it needs to be documented. Please extend the patch to include changes to binutils/doc/binutils.texi and binutils/NEWS. * Please try to follow the GNU coding standard. (In the patch there are several comments that ought to be reformatted to include a terminating period followed by two spaces. Also there are places where there is no space between a function name and its opening parenthesis). Cheers Nick --------------------------------------------------------------------------- request-assign.future: Please email the following information to fsf-records@gnu.org, and we will send you the assignment form for your past and future changes. Please use your full name as the subject line of the message. [What is the name of the program or package you're contributing to?] [Did you copy any files or text written by someone else in these changes? Even if that material is free software, we need to know about it.] [Do you have an employer who might have a basis to claim to own your changes? Do you attend a school which might make such a claim?] [For the copyright registration, what country are you a citizen of?] [What year were you born?] [Please write your email address here.] [Please write your snail address here.] [Which files have you changed so far, and which new files have you written so far?] ---------------------------------------------------------------------------