From: "Luis Peiro" <malfonso@able.es>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: bluez logo
Date: Sat, 19 Feb 2005 15:31:01 +0100 [thread overview]
Message-ID: <cv7itu$bam$1@sea.gmane.org> (raw)
In-Reply-To: 421735F6.2050300@debiancolombia.org
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Great Fredy ! I like the first one, the first position
"Fredy P." <digitalfredy@debiancolombia.org> escribió en el mensaje
news:421735F6.2050300@debiancolombia.org...
Hi all!
I make any desings for the bluetooth logo (
http://pwp.etb.net.co/pulidolopez/img/bluez/ ), what do
you think about it?
--
Suerte and F.S.Fv.
ATT: Fredy P.
___________________________________________________
F.S.Fv. es acrónimo de Free Software Forever
http://www.fsf.org/philosophy/free-sw.es.html
Normas básicas de comportamiento en el ciberespacio
http://www.netiqueta.org/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=ick
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-02-19 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 12:49 [Bluez-users] bluez logo Fredy P.
2005-02-19 14:31 ` Luis Peiro [this message]
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='cv7itu$bam$1@sea.gmane.org' \
--to=malfonso@able.es \
--cc=bluez-users@lists.sourceforge.net \
/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.