From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: 322732-submitter@bugs.debian.org, 322732@bugs.debian.org
Subject: Bug#322732: [Bluez-devel] [Pkg-bluetooth-maintainers] Bug#322732: more on this bug (was: rfcomm bind fails with obscure error message)
Date: Sun, 04 Jun 2006 17:46:54 +0200 [thread overview]
Message-ID: <1149436014.8053.6.camel@localhost> (raw)
In-Reply-To: <20060604151505.GA16780@esaurito.net>
Hi Filippo,
> > > comments?
> >
> > check for EOPNOTSUPP error code and only then print this error.
>
> allright, I fixed this with the attached patch
the patch has been applied to the CVS now. Thanks.
Regards
Marcel
_______________________________________________
Pkg-bluetooth-maintainers mailing list
Pkg-bluetooth-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-bluetooth-maintainers
prev parent reply other threads:[~2006-06-04 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 20:48 [Bluez-devel] more on this bug (was: rfcomm bind fails with obscure error message) Filippo Giunchedi
2006-05-29 13:16 ` [Pkg-bluetooth-maintainers] Bug#322732: " Marcel Holtmann
2006-06-04 15:15 ` Bug#322732: " Filippo Giunchedi
2006-06-04 15:46 ` Marcel Holtmann [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=1149436014.8053.6.camel@localhost \
--to=marcel@holtmann.org \
--cc=322732-submitter@bugs.debian.org \
--cc=322732@bugs.debian.org \
--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;
as well as URLs for NNTP newsgroup(s).