From: Paul Hedderly <bulkpaul@mjr.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
Philip Blundell <pb@nexus.co.uk>,
bluez-devel@lists.sourceforge.net
Subject: Re: Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid)
Date: Wed, 23 Jul 2003 09:12:48 +0100 [thread overview]
Message-ID: <20030723081248.GM3580@wacka.mjr.org> (raw)
In-Reply-To: <5.1.0.14.2.20030624102040.0de55858@unixmail.qualcomm.com>
On Tue, Jun 24, 2003 at 10:31:25AM -0700, Max Krasnyansky wrote:
>
> I think branch is CVS branch is probably a bad idea. Because we want
> to change a lot of things like command names, etc. Which means lots
> of file renames, CVS does not handle that.
Yea. Time to move to arch/tla from CVS.
--
Paul
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-07-23 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 16:42 [Bluez-devel] patch for d-bus support in hcid Philip Blundell
2003-06-20 16:19 ` David Woodhouse
2003-06-21 0:13 ` Max Krasnyansky
2003-06-24 14:00 ` Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid) Stephen Crane
2003-06-24 17:31 ` Max Krasnyansky
2003-06-25 9:17 ` Stephen Crane
2003-06-25 12:15 ` Marcel Holtmann
2003-06-26 17:15 ` Version 3 libs/utils Max Krasnyansky
2003-07-23 8:12 ` Paul Hedderly [this message]
2003-06-24 9:28 ` [Bluez-devel] patch for d-bus support in hcid David Woodhouse
2003-06-24 9:31 ` Philip Blundell
2003-09-04 21:18 ` David Woodhouse
2003-09-04 22:33 ` Philip Blundell
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=20030723081248.GM3580@wacka.mjr.org \
--to=bulkpaul@mjr.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
--cc=pb@nexus.co.uk \
--cc=steve.crane@rococosoft.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