From: Dennis Luehring <dl.soluz@gmx.net>
To: Andrew Jenner <andrew@codesourcery.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: current state of gcc-ia16?
Date: Fri, 08 Jun 2018 12:06:00 -0000 [thread overview]
Message-ID: <28c3af22-296f-b370-6616-f7f4f103c6e2@gmx.net> (raw)
In-Reply-To: <5a6c2a40-7c31-4870-47c3-fb64e8cb20d6@codesourcery.com>
>> is the patch already integrated into mainline?
>No, it's not.
will that ever happen?
>> is this the most recent development place?
>> https://github.com/tkchia/gcc-ia16
>Yes, that's the right place.
thx
Am 08.06.2018 um 12:59 schrieb Andrew Jenner:
> Hi Dennis,
>
> On 08/06/2018 11:37, Dennis Luehring wrote:
> > is the patch already integrated into mainline?
>
> No, it's not.
>
> > is this the most recent development place?
> > https://github.com/tkchia/gcc-ia16
>
> Yes, that's the right place.
>
> Andrew
next prev parent reply other threads:[~2018-06-08 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 10:59 Dennis Luehring
2018-06-08 11:43 ` Andrew Jenner
2018-06-08 12:06 ` Dennis Luehring [this message]
2018-06-08 13:22 ` Andrew Jenner
2018-06-11 19:19 ` Jeff Law
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=28c3af22-296f-b370-6616-f7f4f103c6e2@gmx.net \
--to=dl.soluz@gmx.net \
--cc=andrew@codesourcery.com \
--cc=gcc@gcc.gnu.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).