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] some manual pages patches
Date: Thu, 01 Jun 2006 20:38:03 +0200 [thread overview]
Message-ID: <1149187083.28511.49.camel@localhost> (raw)
In-Reply-To: <20060601180504.GE7486@esaurito.net>
Hi Filippo,
> attached there are a few patches to manual pages (or corrections) collected in
> the debian package, you might want to merge them in the next release.
thanks for the patches. Documentation updates are always welcome. I
applied the hciconfig and hciattach changes, but the l2ping and pand
changes are failing against the latest CVS.
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-01 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 18:05 [Bluez-devel] [PATCH] some manual pages patches Filippo Giunchedi
2006-06-01 18:38 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-03 13:40 Filippo Giunchedi
2006-06-04 13:06 ` 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=1149187083.28511.49.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.