From: James Cameron <james.cameron@hp.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] pand/main.c, restore signals for dev-up script
Date: Tue, 29 Jun 2004 15:23:17 +1000 [thread overview]
Message-ID: <20040629052317.GQ20139@hp.com> (raw)
In-Reply-To: <1088465177.6030.221.camel@pegasus>
On Tue, Jun 29, 2004 at 01:26:17AM +0200, Marcel Holtmann wrote:
> from my view it is better to use "net.agent" and "pand -l" for this job.
Yes, I know. I don't know why you think that though, since using dev-up
costs less in dependencies and execution time. You've proposed removing
dev-up on the grounds that I had problems with it, and that you've never
used it; which suggests that you think that cost of maintenance is more
critical. I'm just guessing.
> If it gets to complex then you should integrate it directly into pand.
dev-up is integrated directly into pand. ;-)
--
James Cameron
next prev parent reply other threads:[~2004-06-29 5:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 13:33 [Bluez-devel] [PATCH] pand/main.c, restore signals for dev-up script James Cameron
2004-06-27 20:06 ` Marcel Holtmann
2004-06-27 23:34 ` James Cameron
2004-06-28 7:44 ` Marcel Holtmann
2004-06-28 8:53 ` James Cameron
2004-06-28 9:05 ` Marcel Holtmann
2004-06-28 9:55 ` James Cameron
2004-06-28 10:13 ` Marcel Holtmann
2004-06-28 10:19 ` James Cameron
2004-06-28 10:39 ` Marcel Holtmann
2004-06-28 12:06 ` James Cameron
2004-06-28 12:54 ` Marcel Holtmann
2004-06-28 22:48 ` James Cameron
2004-06-28 23:26 ` Marcel Holtmann
2004-06-29 5:23 ` James Cameron [this message]
2004-06-29 8:58 ` Marcel Holtmann
2004-06-29 10:55 ` James Cameron
2004-06-29 11:26 ` Marcel Holtmann
2004-06-30 0:15 ` James Cameron
2004-06-30 9:06 ` 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=20040629052317.GQ20139@hp.com \
--to=james.cameron@hp.com \
--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