From: Michael <gdb-patches@cyberfiber.org>
To: gdb-patches@sourceware.org
Subject: Re: patch for testing purposes
Date: Thu, 31 Dec 2009 09:30:00 -0000 [thread overview]
Message-ID: <4B3C6F06.4010000@cyberfiber.org> (raw)
In-Reply-To: <20091230114518.GD548@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
well, hope this will do for the moment then :)
michael
Joel Brobecker wrote:
>> Agreed, do you need any additional information to this end?
>>
>
> Here is the form that you need to complete and send to the FSF
> to get things started. Not sure what you are planning to work on,
> but I have noticed that people who work on GDB sometimes make changes
> to GCC and/or binutils. Since the process takes so long, it might
> be advantageous to list other projects you might be interested to.
> Since I am a big believer in Free Software, I would personally even
> put "ALL" to be done with any paperwork, but I don't know if the FSF
> still allows it or not. If you do put ALL, make sure to make a specific
> list of projects you want included in the assignment forms, in case
> they reject the ALL.
>
> | Please email the following information to assign@gnu.org, and we
> | will send you the assignment form for your past and future changes.
> |
> | Please use your full legal name (in ASCII characters) as the subject
> | line of the message.
> | ----------------------------------------------------------------------
> | REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
> |
> | [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 postal address here.]
> |
> |
> |
> |
> |
> | [Which files have you changed so far, and which new files have you written
> | so far?]
>
>
[-- Attachment #2: gdb-7.0-7.1.tar.gz --]
[-- Type: application/x-gzip, Size: 1213 bytes --]
next prev parent reply other threads:[~2009-12-31 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 7:57 Michael
2009-12-30 8:14 ` Joel Brobecker
2009-12-30 10:21 ` Eli Zaretskii
[not found] ` <4B3B3AB1.5060106@cyberfiber.org>
[not found] ` <20091230114518.GD548@adacore.com>
2009-12-31 9:30 ` Michael [this message]
2009-12-31 11:38 ` Michael
2009-12-31 11:51 ` Joel Brobecker
2009-12-31 22:09 ` Michael
2010-01-01 3:36 ` Joel Brobecker
2010-01-01 7:14 ` Michael
2010-01-01 8:19 ` Joel Brobecker
[not found] ` <20091231114605.GK2788@adacore.com>
2009-12-31 11:56 ` Michael
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=4B3C6F06.4010000@cyberfiber.org \
--to=gdb-patches@cyberfiber.org \
--cc=gdb-patches@sourceware.org \
/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