From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bccmd patch
Date: Mon, 26 Jun 2006 14:23:19 +0200 [thread overview]
Message-ID: <1151324599.7694.13.camel@localhost> (raw)
In-Reply-To: <70DCB28C5BB04A4BBB1C8512589BAC65ED7DE4@MAIL006.mail.lan>
Hi Chris,
> I would have thought that it should be in both the manpage and the
> usage.
the bccmd is a dangerous tool and I prefer people think twice before
they actually use it. So they have at least to read the manual page
first before they are going to render their devices useless.
> > Please update the manpage to include them there.
>
> Patch attached (against 3.1).
The patch has been applied to the CVS. Do you mind adding some
explanation of the possible stores shortcuts?
Regards
Marcel
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-26 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 16:16 [Bluez-users] Bccmd patch Brand, Chris
2006-06-19 18:09 ` Marcel Holtmann
2006-06-19 18:32 ` Brand, Chris
2006-06-20 9:50 ` Marcel Holtmann
2006-06-20 12:08 ` Sumeet VERMA
2006-06-20 18:19 ` Brand, Chris
2006-06-26 12:23 ` Marcel Holtmann [this message]
2006-07-05 18:46 ` [Bluez-users] [PATCH] " Brand, Chris
2006-07-13 16:13 ` [Bluez-users] [PATCH] Bccmd patch - resend Brand, Chris
-- strict thread matches above, loose matches on Subject: below --
2006-04-13 20:40 [Bluez-users] Bccmd patch Brand, Chris
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=1151324599.7694.13.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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).