From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-pr@lists.gentoo.org
Subject: Re: [gentoo-pr] 0-day ebuilds
Date: Sun, 10 Oct 2004 10:26:11 -0700 [thread overview]
Message-ID: <1097429171.10585.3.camel@localhost> (raw)
In-Reply-To: <20041010100114.GC8655@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
On Sun, 2004-10-10 at 12:01 +0200, Sven Vermeulen wrote:
> How would you receive the necessary information? From the packager himself?
That's my thought. Or anyone else observant enough to notice it.
--
Donnie Berkholz
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-10 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 7:47 [gentoo-pr] 0-day ebuilds Donnie Berkholz
2004-10-10 10:01 ` Sven Vermeulen
2004-10-10 17:26 ` Donnie Berkholz [this message]
2004-10-12 14:29 ` Eric G Ortego
2004-10-12 14:51 ` Donnie Berkholz
2004-10-13 10:38 ` Sven Vermeulen
2004-10-13 17:32 ` Donnie Berkholz
2004-10-10 11:59 ` Kurt Lieber
2004-10-10 13:16 ` Sven Vermeulen
2004-10-10 17:25 ` Donnie Berkholz
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=1097429171.10585.3.camel@localhost \
--to=spyderous@gentoo.org \
--cc=gentoo-pr@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