From: Nick Clifton <nickc@redhat.com>
To: "Robert O'Callahan" <rocallahan@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: optimizations for 3x speedup in ld
Date: Thu, 17 Feb 2005 21:05:00 -0000 [thread overview]
Message-ID: <4214C3D2.3080300@redhat.com> (raw)
In-Reply-To: <1108598980.7380.87.camel@meekness.apac.novell.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Hi Rob,
> So ... how do I push this upstream?
Well we would love to have them.
But first things first - can we accept them ? In order for us to accept
them the FSF needs a copyright assignment on file from whomever holds
the copyright on the patches you are contributing. (Presumably either
yourself or the Mozilla Foundation ?) I had a look but could not see
such an assignment in my records, so I guess that obtaining one is the
first step. (If you do have such an assignment, please could you
forward a copy of the confirmation email from the FSF to me ?) I am
attaching a form to fill out and send off to the FSF to get this process
started.
> Should I submit the patch as an
> attachment? It's 69 lines deleted, 458 lines added in ld.h, ldlang.c,
> ldlang.h.
Attachments are fine. Context diffs are great. A ChangeLog entry to
accompany the patch and explain what it does is wonderful.
Cheers
Nick
[-- Attachment #2: future --]
[-- Type: text/plain, Size: 1005 bytes --]
---------------------------------------------------------------------------
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?]
---------------------------------------------------------------------------
next prev parent reply other threads:[~2005-02-17 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 4:43 Robert O'Callahan
2005-02-17 21:05 ` Nick Clifton [this message]
2005-02-17 22:27 ` Robert O'Callahan
2005-02-18 1:54 ` Ian Lance Taylor
2005-02-18 2:02 ` Robert O'Callahan
2005-02-18 21:42 ` Nick Clifton
2005-02-21 11:21 ` Robert O'Callahan
2005-03-29 16:04 ` Jakub Jelinek
2005-03-30 13:17 ` Robert O'Callahan
2005-04-04 17:10 ` 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=4214C3D2.3080300@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=rocallahan@novell.com \
/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).