public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Salvador Eduardo Tropea <salvador@inti.gov.ar>
Cc: binutils@sources.redhat.com
Subject: Re: RFC objdump new feature to generate debug info using ctags style
Date: Mon, 12 May 2003 11:27:00 -0000	[thread overview]
Message-ID: <m3fznkct29.fsf@redhat.com> (raw)
In-Reply-To: <3EB293A4.30103@inti.gov.ar> (Salvador Eduardo Tropea's message of "Fri, 02 May 2003 12:49:56 -0300")

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?]





---------------------------------------------------------------------------

  reply	other threads:[~2003-05-12 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 15:50 Salvador Eduardo Tropea
2003-05-12 11:27 ` Nick Clifton [this message]
2003-05-13 20:09   ` Salvador Eduardo Tropea
2003-05-13 20:35     ` Salvador Eduardo Tropea
2003-05-14  7:05     ` Nick Clifton
2003-07-21 19:32   ` Salvador Eduardo Tropea
2003-07-22 13:34     ` Nick Clifton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3fznkct29.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=salvador@inti.gov.ar \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).