From: Ilija Kocho <ilijak@siva.com.mk>
To: ecos-maintainers@ecos.sourceware.org
Subject: GCC 4.6
Date: Sun, 22 Jan 2012 12:54:00 -0000 [thread overview]
Message-ID: <4F1C06DC.4030005@siva.com.mk> (raw)
Hello colleagues
Some ten days ago I posted a proposal for GCC upgrade to eCos Developers
list: http://ecos.sourceware.org/ml/ecos-devel/2012-01/msg00003.html .
The initiative draw interest and positive reactions from eCos community
developing a discussion; some questions raised and some suggestions
offered. At this point, I find applicable and I accept the suggestion by
John Dallaway to carry-out gradually and initially begin with a test
release.
Considering all mentioned above, if there aren't objections, I would
initiate GCC 4.6.2 test release.
Regards
Ilija Kocho
reply other threads:[~2012-01-22 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F1C06DC.4030005@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-maintainers@ecos.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).