public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: Till Kamppeter <till.kamppeter@gmail.com>,
	linux-bluetooth@vger.kernel.org, Tim Waugh <twaugh@redhat.com>
Subject: Re: PATCHES: Device discovery of the "bluetooth" CUPS backend does not work
Date: Tue, 11 Aug 2009 15:09:47 -0700	[thread overview]
Message-ID: <1250028587.30166.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1249996376.2022.25.camel@localhost.localdomain>

Hi Bastien,

> > Could you put them in? Then I do not need to download the git only to 
> > format two simple one-point-only-changed patches. Thanks.
> 
> Patches attached.
> 
> > >> Do you have a bug/feature request tracking system?
> > > 
> > > There isn't one.
> > 
> > As vluez seems to be a part of the kernel project, does the kernel even 
> > not have a bug tracking system?
> 
> BlueZ's kernel bits probably use the kernel bug tracker. For the
> user-space bits, send mails here[1].

kernel patches and userspace patches should be send to this mailing
list.

Regards

Marcel



  reply	other threads:[~2009-08-11 22:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 20:19 PATCHES: Device discovery of the "bluetooth" CUPS backend does not work Till Kamppeter
2009-08-11 10:33 ` Bastien Nocera
2009-08-11 11:19   ` Till Kamppeter
2009-08-11 11:33     ` Bastien Nocera
2009-08-11 12:24       ` Till Kamppeter
2009-08-11 13:12         ` Bastien Nocera
2009-08-11 22:09           ` Marcel Holtmann [this message]
2009-08-11 22:14           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2009-08-26 17:59 Till Kamppeter
2009-08-26 18:14 ` Marcel Holtmann
2009-08-26 19:12   ` Till Kamppeter
2009-08-27  2:35     ` 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=1250028587.30166.31.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=till.kamppeter@gmail.com \
    --cc=twaugh@redhat.com \
    /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