From: Tamer Higazi <tamer23@myrealbox.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] What happened with bluez.org
Date: Mon, 14 Mar 2005 08:56:12 +0100 [thread overview]
Message-ID: <1110786972.9375.0.camel@tux> (raw)
In-Reply-To: <d1f423d3050313183529b84218@mail.gmail.com>
yes
I had a short time ago problems accessing it.
On Sun, 2005-03-13 at 18:35 -0800, Anderson Rodrigues wrote:
> Hi folks,
>
>
> I am having difficults on accessing www.bluez.org. Does anybody have
> the same problem?
>
> thanks
>
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-14 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 2:35 [Bluez-users] What happened with bluez.org Anderson Rodrigues
2005-03-14 7:56 ` Tamer Higazi [this message]
2005-03-14 10:14 ` Marcel Holtmann
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=1110786972.9375.0.camel@tux \
--to=tamer23@myrealbox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox