From: ligang@sunnorth.com.cn
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: re: Re: [patch] add target Score to Binutils
Date: Tue, 19 Sep 2006 11:48:00 -0000 [thread overview]
Message-ID: <OFF8C3B71F.829E6A98-ON482571EE.002B4197-482571EE.003A7725@sunnorth.com.cn> (raw)
In-Reply-To: <450C8FC9.8070402@redhat.com>
Nick Clifton <nickc@redhat.com> wrote on 2006-09-17 07:59:05:
> Hi Ligang,
>
> > I had done the whole process of copyright assignment with the FSF.
> > Attachment is the ASSIGNMENT.
>
> Thank you. It appears that I am not being informed of recent copyright
> assignments, so I was unaware of this. I will endevour to make sure
> that I am informed in the future.
>
> In the meantime I have checked in your submission. I did have quite a
> few problems with it, and normally I would have asked you to resubmit
> it, but I felt quite guilty at how long it had taken me to getting round
> to reviewing the patch. For future reference however please bear these
> points in mind:
>
> * Please provide the code as context diffs against the current
> sources in the mainline of the CVS repository. Hinting at where the
> changes ought to made in the generic files is not good enough, and
> providing code that does not compile because it uses functions that no
> longer exist is a very bad idea.
>
> * Please include ChangeLog entries with your patches. These should
> not be in the form of context diffs, just ordinary ascii.
>
> * Please run the binutils testsuites and ensure that there are no
> regressions.
ok. I will follow these points.
> One other thing - your submission included a suggested change to the top
> level config.sub file. This file is not part of the binutils project
> and you will need to submit a separate patch to have it changed. This
> patch should be sent to config-patches@gnu.org.
I have sent the change of config.sub to config-patches@gnu.org.
What is the next step to enter binutils main tree?
> Cheers
> Nick
>
next parent reply other threads:[~2006-09-19 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <450C8FC9.8070402@redhat.com>
2006-09-19 11:48 ` ligang [this message]
2006-09-25 16:14 ` Nick Clifton
2006-09-26 8:14 ` ligang
2006-09-26 14:18 ` Nick Clifton
2006-09-27 22:32 ` ligang
2006-09-12 2:38 梅丽刚
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=OFF8C3B71F.829E6A98-ON482571EE.002B4197-482571EE.003A7725@sunnorth.com.cn \
--to=ligang@sunnorth.com.cn \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).