From: Tom Gall <tom_gall@mac.com>
To: john_davis@pauldavisautomation.com
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo's policy on sender id
Date: Sun, 5 Sep 2004 11:26:30 -0500 [thread overview]
Message-ID: <58395A8E-FF58-11D8-9CE6-0003939E069A@mac.com> (raw)
In-Reply-To: <1094392845.2540.14.camel@woot.uberdavis.com>
On Sep 5, 2004, at 9:00 AM, John Davis wrote:
> Hi all -
> Recent [1] announcements [2] from other large projects have prompted
> this inquiry - should Gentoo adopt similar policies regarding Sender ID
> and make a public statement or is it not worth our time?
Personally I wonder how much of the attention with regards to Sender ID
is more of a dig against micro$oft. O wait that's the "in" thing to
do. :-)
But what does saying something really mean? Would it be somewhat sorta
like the xfree86 license change situation?
IE we won't have any package in portage that implements Sender ID?
Regards,
Tom
> 1. http://it.slashdot.org/article.pl?sid=04/09/05/138257&tid=111&tid=1
> 2.
> http://apache.slashdot.org/article.pl?sid=04/09/02/
> 1446229&tid=148&tid=155&tid=109&tid=95
> --
> John Davis
> Gentoo Linux Developer
> <http://dev.gentoo.org/~zhen>
>
> ----
> GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
> Fingerprint: 4F9E 41F6 D072 5C1A 636C 2D46 B92C 4823 E281 41BB
>
Tom Gall
Gentoo/PPC64 Team Leader
tgall@gentoo.org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-05 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 14:00 [gentoo-dev] gentoo's policy on sender id John Davis
2004-09-05 16:26 ` Tom Gall [this message]
2004-09-05 19:24 ` Chris Bainbridge
2004-09-05 20:33 ` Stephen P. Becker
2004-09-05 21:33 ` Nicholas Jones
2004-09-06 10:29 ` Chris Bainbridge
2004-09-06 18:36 ` [gentoo-dev] Re: [gentoo-core] " Nicholas Jones
2004-09-16 4:38 ` Rob Cakebread
2004-09-16 14:02 ` Malte S. Stretz
2004-09-05 23:44 ` Kurt Lieber
2004-09-16 23:25 ` Michiel de Bruijne
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=58395A8E-FF58-11D8-9CE6-0003939E069A@mac.com \
--to=tom_gall@mac.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=john_davis@pauldavisautomation.com \
/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