All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: SELinux Mailing List <selinux@tycho.nsa.gov>
Subject: Re: Logo Artwork for SELinux?
Date: Wed, 14 Apr 2004 11:05:38 +0200	[thread overview]
Message-ID: <20040414110538.D26635@lemuria.org> (raw)
In-Reply-To: <3162.204.169.68.12.1081781856.squirrel@webmail.ods.org>; from elvedin@ods.org on Mon, Apr 12, 2004 at 09:57:36AM -0500

On Mon, Apr 12, 2004 at 09:57:36AM -0500, Elvedin Trnjanin wrote:
> I suggest we avoid any preference to a country or orginization (US or UN)
> and just perhaps go with some cryptography related thing, random numbers
> (1s, 0s) in the background or something of that sort.

How about using the proposed light-blue UN colour for the random number
strings (why random? let's give the geeks something to do and have it
actually mean something).

Add Tux with chainmail shirt.

Plus a simple "SELinux" as text.


I'll see what I can whip up. I'm by far no graphics dude, but I know a
little about gimp.


-- 
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2004-04-14  9:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 22:56 Logo Artwork for SELinux? Bill Laut
2004-04-04 22:11 ` Chris
2004-04-05 20:07   ` Bill Laut
2004-04-05 22:57     ` Bill McCarty
2004-04-06  5:06       ` Michael Pender
2004-04-06 14:51         ` Dan Thomsen
2004-04-07  2:03           ` Joshua Brindle
2004-04-07  4:57             ` Douglas Williams
2004-04-07  5:29             ` Bill Laut
2004-04-07  3:07           ` Douglas Williams
2004-04-07  5:22           ` Bill Laut
2004-04-07  8:36             ` Dale Amon
2004-04-08  3:43             ` Michael Pender
2004-04-08 13:45               ` Dan Thomsen
2004-04-05 14:24 ` Valdis.Kletnieks
2004-04-05 21:11   ` Kerry Thompson
2004-04-05 22:56   ` Dean Anderson
2004-04-06  2:25     ` Bill Laut
2004-04-05 15:54 ` Frank Mayer
2004-04-06  1:44 ` Joshua Brindle
2004-04-10 11:07 ` Russell Coker
2004-04-10 16:08   ` Matthew J. Fanto
2004-04-10 21:24     ` Dale Amon
2004-04-12  7:29       ` Dean Anderson
2004-04-12 14:57         ` Elvedin Trnjanin
2004-04-12 15:14           ` Dale Amon
2004-04-12 15:18             ` Elvedin Trnjanin
2004-04-12 22:59               ` Tom Mitchell
2004-04-12 15:35             ` Stephen Smalley
2004-04-12 15:42             ` Russell Coker
2004-04-12 20:11             ` todd glassey
2004-04-13  0:21               ` Michael Pender
2004-04-13 14:33                 ` todd glassey
2004-04-14  9:05           ` Tom [this message]
2004-04-11  2:44     ` Russell Coker
  -- strict thread matches above, loose matches on Subject: below --
2004-04-13 14:57 Dowd, Alan S
2004-04-14  9:10 ` Tom
2004-04-14 13:37   ` todd glassey
     [not found] <BCA3701A.9ED9%michael.pender@nanochron.com>
2004-04-15  5:26 ` Russell Coker

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=20040414110538.D26635@lemuria.org \
    --to=tom@lemuria.org \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.