public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Rahmatullin <wrar@altlinux.ru>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Should hcid wait for dbus daemon?
Date: Sat, 13 Jan 2007 22:39:37 +0500	[thread overview]
Message-ID: <20070113173937.GA11400@wrars-comp.wrarsdomain> (raw)
In-Reply-To: <200701081837.04388.dgollub@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 140 bytes --]

+1, we in ALT Linux use exactly the same scheme for launching hcid and we
also want to fix this issue.

-- 
WBR, wRAR (ALT Linux Team)

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2007-01-13 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 17:37 [Bluez-devel] Should hcid wait for dbus daemon? Daniel Gollub
2007-01-08 18:47 ` Johan Hedberg
2007-01-08 23:31   ` Luca Capello
2007-01-09  0:01     ` Daniel Gollub
2007-01-09  8:27     ` Stefan Seyfried
2007-01-08 23:41   ` Daniel Gollub
2007-01-12 15:25     ` Stefan Seyfried
2007-01-13 17:39 ` Andrey Rahmatullin [this message]
2007-01-15 13:30 ` 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=20070113173937.GA11400@wrars-comp.wrarsdomain \
    --to=wrar@altlinux.ru \
    --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