From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: <bluez-devel@lists.sourceforge.net>, <ekiga-devel-list@gnome.org>
Subject: [Bluez-devel] Common file "sbc.c" in Ekiga/Opal and Bluez
Date: Wed, 29 Oct 2008 12:02:29 +0100 [thread overview]
Message-ID: <003001c939b5$d685da50$83918ef0$@de> (raw)
Hello,
I just want to hint to the fact that the file in "sbc.c" containing the
Bluetooth audio codec appears twice in the repository of Ekiga/Opal =
> svn co https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk
opal/plugins/audio/SBC/sbc.c
and as file "bluez/sbc/sbc.c" in
git://git.kernel.org/pub/scm/bluetooth/bluez.git.
Maybe, somebody has an idea to keep both versions in sync if one is
changing? Or is it not necessary?
Best regards,
Christian
--------------------------------------------------------
Dr.-Ing. Christian Hoene
Computer Networks and Internet, University of T=FCbingen
Sand 13, 72076 T=FCbingen, Germany, Phone +49 7071 2970532
http://net.informatik.uni-tuebingen.de/~hoene
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-10-29 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 11:02 Christian Hoene [this message]
2008-10-29 18:41 ` [Bluez-devel] Common file "sbc.c" in Ekiga/Opal and Bluez Marcel Holtmann
2008-10-29 19:39 ` Christian Hoene
2008-10-30 18:06 ` Marcel Holtmann
2008-10-31 0:04 ` Craig Southeren
2008-10-31 7:09 ` 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='003001c939b5$d685da50$83918ef0$@de' \
--to=hoene@uni-tuebingen.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ekiga-devel-list@gnome.org \
/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