Linux bluetooth development
 help / color / mirror / Atom feed
From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth-alsa website cleanup
Date: Fri, 24 Nov 2006 16:48:08 +0100	[thread overview]
Message-ID: <45671438.5000604@palmsource.com> (raw)
In-Reply-To: <45649452.6050904@xmission.com>

Brad,

If the current cvs is stable enough, I think it is a good idea to =

release it.
However, I have a patch on the grill so I would like you to be careful =

if you move the source now so that I could repost my patch easily. It =

should be ready by the end of next week.
I still have a few problems to solve and I will start looking at the =

DBUS api. The patch will contain unix sockets, less threads, new avrcp =

commands, sdp records, cleaner traces, plus a try to send sound using sco.

Regards,
Fr=E9d=E9ric.


Brad Midgley a =E9crit :
> Oh...
>
> I forgot to mention that this was the last checklist item for a snapshot
> release. I'll be calling it btsco-0.5. I will be moving the alsa plugins
> to a different source control module after this and won't be making any
> new btsco releases.
>
> Please let me know if you see any issues that need to be addressed first.
>
> Brad
>
>   =

>> fyi, I merged our various sources of documentation and put everything =

>> together in a fairly spartan tabbed interface.
>>
>> http://bluetooth-alsa.sf.net/
>>
>> Brad
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> Bluez-devel mailing list
>> Bluez-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>>     =

>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>   =



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-11-24 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  8:24 [Bluez-devel] bluetooth-alsa website cleanup Brad Midgley
2006-11-22 18:17 ` Brad Midgley
2006-11-24 15:48   ` Frédéric DALLEAU [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=45671438.5000604@palmsource.com \
    --to=frederic.dalleau@palmsource.com \
    --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