public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] More PIN quirks
Date: Sat, 29 Nov 2008 18:32:05 +0100	[thread overview]
Message-ID: <49317C95.7060808@powercraft.nl> (raw)
In-Reply-To: <1227976757.26649.2692.camel@cookie.hadess.net>

Bastien Nocera wrote:
> This builds on top of the move to a PIN database.
> 
> This fixes all but one bug filed against the wizard in the GNOME
> bugzilla.
> 
> I hope it shows that the PIN database is workable.
> 
> Cheers
> 

Thank you Bastien for your hard work!

I have a few questions about these kind of patches, would it not be
easer to maintainable and more usefull to add this kind of information
separate from gnome related packages, and move them to a desktop
independent configuration?

Of course there is nothing wrong with using gnome bugreports or using
gnome applications with the data. However I have seen a lot of patches
that apply to the gnome wizard application and the commandline tools or
kde tools do not use this information, but it would really like the same
functionality in the command line tools so it does work platform
independent.

I know there is not much priority on fixing a commandline tool but, it
can be smart to move device specific info into a general system that all
user frontend systems can use. This will make it a lot easer of other
developers to create new frontends that do not need to reverse engineer
the gnome apps and create duplicated hard to maintain code....

Does this make any sense? Or is there just no time or do we not care
about other users then gnome?

Best regards,

Jelle

      reply	other threads:[~2008-11-29 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 16:39 [PATCH] More PIN quirks Bastien Nocera
2008-11-29 17:32 ` Jelle de Jong [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=49317C95.7060808@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox