public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Support @ SphereHosting.Ca" <support@spherehosting.ca>
To: "gentoo-hardened@lists.gentoo.org" <gentoo-hardened@lists.gentoo.org>
Subject: [gentoo-hardened] Re: [CASE ID:37] Digest of gentoo-hardened@lists.gentoo.org issue 217 (2759-2765)
Date: Tue, 27 Oct 2009 08:11:06 -0400	[thread overview]
Message-ID: <781f3693c029cf0bde6b7bf516b7f453@spherehosting.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

Hello, Your email was received by our support team. They will contact you as soon as possible to awnser your request.&nbsp;You can visite our website www.spherehosting.ca for more information.If this is a sales question please contact sales@spherehosting.ca&nbsp;Thank you,Support Team @ SphereHosting.Ca 
On  27-10-2009, 08:00, gentoo-hardened+help@lists.gentoo.org wrote:Topics (messages 2759 through 2765):

[gentoo-hardened] Re: [CASE ID:34] Digest of gentoo-hardened@lists.gentoo.org issue 216 (2747-2758)
      2759 - "Support @ SphereHosting.Ca" 

[gentoo-hardened] Re: GCC 4.3.4 going stable on Hardened SELinux?
      2760 - Mike Edenfield 

[gentoo-hardened] util-vserver broken after upgrade to gcc-4.3.4
      2761 - Ed W 

[gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened
      2762 - Kakou 

[gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened
      2763 - Ed W 

[gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened
      2764 - Kakou 

[gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened
      2765 - Magnus Granberg


[-- Attachment #2: Type: text/html, Size: 1920 bytes --]

                 reply	other threads:[~2009-10-27 12:11 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=781f3693c029cf0bde6b7bf516b7f453@spherehosting.ca \
    --to=support@spherehosting.ca \
    --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