Linux bluetooth development
 help / color / mirror / Atom feed
From: Stephen Crane <steve.crane@rococosoft.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: 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: 25 Jun 2003 10:17:06 +0100	[thread overview]
Message-ID: <1056532626.1645.162.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <5.1.0.14.2.20030624102040.0de55858@unixmail.qualcomm.com>

On Tue, 2003-06-24 at 18:31, Max Krasnyansky wrote:
> At 07:00 AM 6/24/2003, Stephen Crane wrote:
> >How do you want to start version 3?  We'll need to keep the old utils
> >and libs around for a while. However I'd like to merge SDP in early:
> >there's a lot of duplicated effort (lists, etc.) which can be stripped
> >out.
> >
> >I have the first-cut at this merge in my local tree. However I don't
> >want to check it in on top of the old utils and libs --- unless you
> >think that's OK.
> >
> >So maybe the best way to proceed is to start a new branch in CVS?
> 
> 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.
> 
> How about creating completely new modules
>         libs2 
>         utils2
> and start with the clean history.
> We'll keep old ones around for a while but will only make minor fixes
> to them.

That works for me. You want to go first?

Steve
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-06-25  9:17 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 [this message]
2003-06-25 12:15       ` Marcel Holtmann
2003-06-26 17:15         ` Version 3 libs/utils Max Krasnyansky
2003-07-23  8:12       ` Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid) Paul Hedderly
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=1056532626.1645.162.camel@baroque.rococosoft.com \
    --to=steve.crane@rococosoft.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    --cc=pb@nexus.co.uk \
    /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