DragonFly users List (threaded) for 2008-01
DragonFly BSD
DragonFly users List (threaded) for 2008-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[no subject]


From: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>
Subject: Re: cvsup
Date: Mon, 21 Jan 2008 13:56:45 +0100
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:users@crater.dragonflybsd.org>
List-Subscribe: <mailto:users-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:users-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:users-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-users@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <slrnfoqcit.k9s.vs1@quark.hightek.org>    <478D3794.2040400@fs.ei.tum.de> <slrnfoqu3g.gd8.vs1@quark.hightek.org>    <478DF803.3000400@fs.ei.tum.de> <slrnfp0rjk.5v5.vs1@quark.hightek.org>    <4790a882$0$856$415eb37d@crater_reader.dragonflybsd.org>    <slrnfp3ctd.fm0.vs1@quark.hightek.org> <2978.> <200801210216.m0L2GeoS067253@apollo.backplane.com> <47945286.105@fs.ei.tum.de> <47948274$0$847$415eb37d@crater_reader.dragonflybsd.org
In-Reply-To: <47948274$0$847$415eb37d@crater_reader.dragonflybsd.org>
Sender: users-errors@crater.dragonflybsd.org
Errors-To: users-errors@crater.dragonflybsd.org
Lines: 24
X-Trace: 1200920677 crater_reader.dragonflybsd.org 848
Xref: crater_reader.dragonflybsd.org dragonfly.users:10340

Bill Hacker wrote:
> CVS has been the 'compromise' that is at least not harmful or overly
> demanding.

CVS *is* harmful.  I can't run a patch and work on a different issue
myself - I'll mix both.  Or I'll have to check out into another tree and
lose the patch.

> Rather than 'nag' - set up what you want and see who joins or lends a hand.

It is really cumbersome to keep any repo synchronized, especially if you
want to have a nice repo which reflects vendor branches correctly.
Basically all manual CVS interference has to be dealt with either in the
tool or manually.

> If it adds enough value to enough people, bandwidth and storage will be
> attracted to the solution.

Bandwidth and storage isn't the issue.  I can develop forever in my git
repo, and nobody might ever notice.  And it won't magically make the
project switch from CVS.


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]