From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
Philip Blundell <pb@nexus.co.uk>,
BlueZ Mailing List <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 14:15:47 +0200 [thread overview]
Message-ID: <1056543354.10001.136.camel@pegasus> (raw)
In-Reply-To: <5.1.0.14.2.20030624102040.0de55858@unixmail.qualcomm.com>
Hi Max,
Hi Stephen,
> 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.
we have already discussed this and starting with new modules seemed to
be the cleanest way. But we shouldn't name them libs2 and utils2,
because we are already at version 2.x with the others. We should use
libs3 and utils3 or maybe an unrelated to the version number suffix like
"-ng".
If we agree on the new name, I will start to create the framework for
the new modules.
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-06-25 12:15 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 [this message]
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=1056543354.10001.136.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.