From: James Courtier-Dutton <James@superbug.co.uk>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Qualified :)
Date: Thu, 14 Apr 2005 16:46:28 +0100 [thread overview]
Message-ID: <425E9054.10808@superbug.co.uk> (raw)
In-Reply-To: <1113496342.8989.50.camel@pegasus>
Marcel Holtmann wrote:
>
> The only option that I see to get this really clean is to create a
> non-profit organization that takes care of such things. However I don't
> really have time for this paperwork, but if someone wants to go this
> way, I am in.
>
> Regards
>
> Marcel
>
Isn't that what the FSF is for?
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-14 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 15:52 [Bluez-devel] Qualified :) Dimitry Andric
2005-04-14 16:13 ` Peter Wippich
2005-04-14 16:32 ` Marcel Holtmann
2005-04-14 15:46 ` James Courtier-Dutton [this message]
2005-04-14 16:57 ` Marcel Holtmann
2005-04-14 16:23 ` 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=425E9054.10808@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=bluez-devel@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