From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] [PATCH] rfcomm 'anycommand' bug
Date: Fri, 02 Jun 2006 17:09:11 +0200 [thread overview]
Message-ID: <1149260951.23555.7.camel@localhost> (raw)
In-Reply-To: <20060602115519.GA17462@esaurito.net>
Hi Filippo,
> as reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=229167 rfcomm
> silently exits (or better, does a print_dev_list()) if an unknown command
> without parameters is passed. attached there is a patch (of the 'works-here'
> type) which should solve the problem.
this patch is totally messed up. Unless someone fixes the coding style,
I am not even looking at it.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-02 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 11:55 [Bluez-devel] [PATCH] rfcomm 'anycommand' bug Filippo Giunchedi
2006-06-02 15:09 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-03 13:57 Filippo Giunchedi
2006-06-04 13:19 ` 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=1149260951.23555.7.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.