From: "Kazi Ferdous" <kferdous@gmail.com>
To: gentoo-user+unsubscribe@lists.gentoo.org
Cc: gentoo-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org,
gentoo-dev-announce@lists.gentoo.org,
gentoo-project@lists.gentoo.org,
gentoo-security@lists.gentoo.org, gentoo-gwn@lists.gentoo.org,
gentoo-doc@lists.gentoo.org, gentoo-doc-cvs@lists.gentoo.org,
gentoo-translators@lists.gentoo.org,
gentoo-ppc-user@lists.gentoo.org,
gentoo-ppc-dev@lists.gentoo.org
Subject: [gentoo-security]
Date: Mon, 6 Aug 2007 02:20:38 -0400 [thread overview]
Message-ID: <147ff4620708052320x6ed9c431o260ceb6d5c516088@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: text/html, Size: 5 bytes --]
next reply other threads:[~2007-08-06 6:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 6:20 Kazi Ferdous [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 6:21 [gentoo-security] qubin
2011-01-05 10:40 [gentoo-security] Philipp Günther | Corpex Internet GmbH
2008-10-21 11:23 [gentoo-security] Behzat Erte
2008-10-21 11:19 [gentoo-security] Behzat Erte
2008-08-06 14:12 [gentoo-security] Joe Nolting
2008-02-28 20:50 [gentoo-security] Darren Taylor
2008-02-11 16:37 [gentoo-security] Dominik Zalewski
2007-02-01 8:42 [gentoo-security] shadowmind
2006-09-28 12:27 [gentoo-security] Orlenko Stas
2006-03-21 16:43 [gentoo-security] John Paine
2006-01-18 11:15 [gentoo-security] tfn2k tfn2k
2006-01-18 11:40 ` [gentoo-security] Taka John Brunkhorst
2006-01-18 11:54 ` [gentoo-security] Stuart Howard
2006-01-18 12:30 ` [gentoo-security] Taka John Brunkhorst
2006-01-18 11:07 [gentoo-security] tfn2k tfn2k
2005-11-09 13:38 [gentoo-security] Bernd Lippert
2005-10-13 14:36 [gentoo-security] jc_cts
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=147ff4620708052320x6ed9c431o260ceb6d5c516088@mail.gmail.com \
--to=kferdous@gmail.com \
--cc=gentoo-announce@lists.gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
--cc=gentoo-gwn@lists.gentoo.org \
--cc=gentoo-ppc-dev@lists.gentoo.org \
--cc=gentoo-ppc-user@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=gentoo-security@lists.gentoo.org \
--cc=gentoo-translators@lists.gentoo.org \
--cc=gentoo-user+unsubscribe@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