All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: compat/Makefile.am manpages fix / pand/dund question
Date: Mon, 24 Nov 2008 12:00:37 +0100	[thread overview]
Message-ID: <20081124110037.GC28799@suse.de> (raw)
In-Reply-To: <226D5095-C45F-49D8-8001-9D62F17D8122@holtmann.org>

Hi Marcel,

On Mon, Nov 24, 2008 at 03:58:11AM +0100, Marcel Holtmann wrote:
>> package? I guess that I should not package hidd, no matter how much
>> users would like it, though ;-)
>
> You can put hidd in bluez-compat if you like. It is useful for debugging 
> since it can show the actual kernel state of the hidp.ko module.

Fortunately nobody has requested it for quite some time.
Would it be helpful to remove the "--server" code from hidd, since I guess
that this will not be useful anymore (and I fear that once I package up
hidd, people _will_ use "hidd --server", because they read that in some
outdated README). I can come op with a patch for that, if wanted.

Thanks,

	seife
-- 
Stefan Seyfried
R&D Team Mobile Devices            |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." 

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

      reply	other threads:[~2008-11-24 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  9:20 compat/Makefile.am manpages fix / pand/dund question Stefan Seyfried
2008-11-24  2:58 ` Marcel Holtmann
2008-11-24 11:00   ` Stefan Seyfried [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=20081124110037.GC28799@suse.de \
    --to=seife@suse.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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.