From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] New keytab storage
Date: Sat, 31 Jan 2004 17:03:32 +0100 [thread overview]
Message-ID: <1075565012.14644.176.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1075564322.2720.42.camel@pegasus>
lör 2004-01-31 klockan 16.52 skrev Marcel Holtmann:
> But I think we should discuss some design goals of the new device manager.
Great idea. What's your plan for it?
> I don't see what kind of mess in "glib-ectomy" you mean, but go ahead
> and send a patch for it.
Some bads, I think:
- The API can be improved
- Tons of ugly (even in opionon) typedef:s
- No style
Fredrik
next prev parent reply other threads:[~2004-01-31 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 23:56 [Bluez-devel] [PATCH] New keytab storage Fredrik Noring
2004-01-31 0:32 ` Marcel Holtmann
2004-01-31 0:55 ` Fredrik Noring
2004-01-31 1:18 ` Marcel Holtmann
2004-01-31 9:27 ` Fredrik Noring
2004-01-31 15:23 ` Marcel Holtmann
2004-01-31 15:40 ` Fredrik Noring
2004-01-31 15:52 ` Marcel Holtmann
2004-01-31 16:03 ` Fredrik Noring [this message]
2004-01-31 18:01 ` Marcel Holtmann
2004-01-31 18:15 ` Fredrik Noring
2004-01-31 10:47 ` Fredrik Noring
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=1075565012.14644.176.camel@akka.yeti.nocrew.org \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox