From: Magnus Granberg <zorry@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Meeting 2010-06-16
Date: Thu, 17 Jun 2010 13:32:20 +0200 [thread overview]
Message-ID: <201006171332.20316.zorry@gentoo.org> (raw)
Meeting 2010-06-16
1.0 Toolchain
We have started to move >= gcc 4.4 and SSP support to the tree.
If all goes well it will bee in the tree this weekend masked for
we still need to wait for some packages to get bumped.
GCC 4.4.3 will be the target to get stable GCC 4.5.0 will be in the
tree later on when some patchses is okey upstream.
2.0 Kernel
We have the 2.6.32 in the tree for testing and it have work fine this
far. 2.6.32-r9 will bee the stable one if nothing show up.
We will try to keep .32 as long term kernel as upstream do.
Next cutting edge kernel will bee .34 or .35 so no .33
3.0 Profiles
We haven't done anythig about it but we do have plan.
Most is that we lack the time to work with it.
4.0 Docs
Still need alot of work and we lack the time to work with it.
Hope we can work with it more when we have got the toolchain
and kernel up to date and the bug list down.
/blueness Chainsaw solar Zorry
next reply other threads:[~2010-06-17 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 11:32 Magnus Granberg [this message]
2010-06-17 16:27 ` [gentoo-hardened] Meeting 2010-06-16 Ed W
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=201006171332.20316.zorry@gentoo.org \
--to=zorry@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.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