From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Cached friendly names never updated when changed
Date: Thu, 27 Mar 2008 16:24:20 +0100 [thread overview]
Message-ID: <47EBBC24.50604@idlum.be> (raw)
In-Reply-To: <8AE6C0B8-481C-4388-B089-B78050E7E6E2@holtmann.org>
Hi Marcel,
> this indeed looks like a bug. Seems like the new name is not written
> to disk. Can you re-produce this with bluez-utils-3.29?
Ok, I'll upgrade this box to 3.29 and try to reproduce it. FYI this
output comes from a box running v3.28.
Regards,
Pierre-Yves
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-03-27 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 16:56 [Bluez-devel] Cached friendly names never updated when changed Pierre-Yves Paulus
2008-03-26 17:05 ` Marcel Holtmann
2008-03-27 13:11 ` Pierre-Yves Paulus
2008-03-27 15:06 ` Marcel Holtmann
2008-03-27 15:24 ` Pierre-Yves Paulus [this message]
2008-03-27 15:45 ` 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=47EBBC24.50604@idlum.be \
--to=py@idlum.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox