public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Fred Cooke <fred.cooke@gmail.com>
To: binutils@sourceware.org
Subject: Re: 68hc11/12/s12x/xgate patch
Date: Tue, 20 Dec 2011 22:29:00 -0000	[thread overview]
Message-ID: <CABZhLO-Ye-G1nYW1eqpdjnYG1W4zaKq+TvgzFBebJk4ash5mtg@mail.gmail.com> (raw)
In-Reply-To: <1324419607.8652.84.camel@jsm2>

To the maintainers: I would recommend holding off a little longer on
accepting this into the upstream repository. I head a project that
uses these tools and I believe there are some issues with this patch
that are yet to be shown. There should be more information available
inside the next 24 hours. Hopefully that is not too long to wait.

Thank you in advance for your patience.

Regards,

Fred.

On Tue, Dec 20, 2011 at 11:20 PM, James Murray <jsm@jsm-net.demon.co.uk> wrote:
>
> Back in March, James Murray wrote:
> > On Tue, 2011-03-15 at 08:34 +0000, Nick Clifton wrote:
> > > First of all, I must point out that we do not appear to have a FSF
> > > Copyright Assignment on file from you.
>
> Now completed and returned to me.
>
> > > As for the patch itself, it is fine apart from one problem - it
> > > introduces some new gas testsuite failures to the m68hc11-elf target.
>
> I believe I resolved those problems and as per recent posts now have
> the testsuite "make check" running cleanly on my system.
>
> Find attached updated patch against CVS as of 21:35 GMT 20th Dec 2011.
>
> regards
>
> James Murray
>

  reply	other threads:[~2011-12-20 22:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 22:22 James Murray
2011-03-07 16:35 ` James Murray
2011-03-15  8:33   ` Nick Clifton
2011-03-15 15:08     ` James Murray
2011-12-20 22:20       ` James Murray
2011-12-20 22:29         ` Fred Cooke [this message]
2011-12-20 23:23           ` James Murray
2011-12-21 22:29             ` Fred Cooke
2011-12-22 16:52               ` Sean Keys
2011-12-22 17:37               ` James Murray
2012-01-05 22:03                 ` James Murray
2012-01-05 23:11                   ` Fred Cooke
2012-01-10 14:42                   ` nick clifton
2012-01-10 15:45                     ` James Murray
2012-01-12 19:39                       ` 68hc11/12/s12x/xgate patch - style question James Murray
2012-01-12 20:14                         ` Fred Cooke
2012-02-26 23:54                     ` 68hc11/12/s12x/xgate patch James Murray
2012-03-12 15:07                       ` James Murray
2012-03-12 15:26                         ` Fred Cooke
2012-03-13 20:28                           ` James Murray
2012-03-13 20:56                             ` Fred Cooke
2012-04-02 12:37                         ` James Murray
2012-04-23 17:05                           ` James Murray
     [not found]                             ` <1337003987.27195.60.camel@jsm2>
2012-05-15 12:59                               ` nick clifton
2012-05-15 18:38                                 ` Fred Cooke
2012-05-15 20:26                                 ` James Murray

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=CABZhLO-Ye-G1nYW1eqpdjnYG1W4zaKq+TvgzFBebJk4ash5mtg@mail.gmail.com \
    --to=fred.cooke@gmail.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).