From: Bryan Hundven <bryanhundven@gmail.com>
To: Titus von Boxberg <titus@elbe-informatik.de>
Cc: crossgcc maillist <crossgcc@sourceware.org>,
Alexey Neyman <aneyman@lynx.com>
Subject: Re: ct-ng is fun
Date: Wed, 18 Apr 2018 21:50:00 -0000 [thread overview]
Message-ID: <CAJ+oik3f2tw+oAfJOWNYjo4gjRZ+HewFPNo6YrTO3+_m76sQrA@mail.gmail.com> (raw)
In-Reply-To: <a200968b22cf4e1394ac3276fb9de8cb@elbe-informatik.de>
On Wed, Apr 18, 2018, 3:26 PM Titus von Boxberg <titus@elbe-informatik.de>
wrote:
> Hi Alexey,
>
> just wanted to let you know that ct-ng is working very well for me.
> It successfully built ppc, arm and x86 linux target toolchains as well as
> an atmel avr cross compiler, each both for linux and mingw32 hosts.
>
> Thanks a lot and keep up the good work.
> Best regards,
> Titus
>
This has been one of my favorite projects to work on, and Alexey has made
some of the best improvements, and I'm very proud of this project and his
improvements.
:cheers:
-Bryan
>
prev parent reply other threads:[~2018-04-18 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 19:26 Titus von Boxberg
2018-04-18 21:50 ` Bryan Hundven [this message]
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=CAJ+oik3f2tw+oAfJOWNYjo4gjRZ+HewFPNo6YrTO3+_m76sQrA@mail.gmail.com \
--to=bryanhundven@gmail.com \
--cc=aneyman@lynx.com \
--cc=crossgcc@sourceware.org \
--cc=titus@elbe-informatik.de \
/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).