From owner-freebsd-hackers@FreeBSD.ORG  Thu Jan  8 10:13:28 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B2DA616A4CE
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 Jan 2004 10:13:28 -0800 (PST)
Received: from opiate.soulwax.net (i216-58-30-170.avalonworks.net
	[216.58.30.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E0FD043D49
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 Jan 2004 10:13:26 -0800 (PST)
	(envelope-from chopra@opiate.soulwax.net)
Received: by opiate.soulwax.net (Postfix, from userid 1001)
	id CB114405B; Thu,  8 Jan 2004 13:05:52 -0500 (EST)
Date: Thu, 8 Jan 2004 13:05:52 -0500
From: Munish Chopra <chopra@soulwax.net>
To: freebsd-hackers@freebsd.org
Message-ID: <20040108180552.GA17378@opiate.soulwax.net>
Mail-Followup-To: freebsd-hackers@freebsd.org
References: <Pine.NEB.3.96L.1040107151556.6025A-100000@fledge.watson.org>
	<1073582974.37229.8.camel@herring.nlsystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1073582974.37229.8.camel@herring.nlsystems.com>
Subject: Re: Where is FreeBSD going?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2004 18:13:28 -0000

On 2004-01-08 17:29 +0000, Doug Rabson wrote:

[...]

> 
> The three main showstoppers for moving FreeBSD to subversion would be:
> 
> 1. A replacement for cvsup. Probably quite doable using svnadmin
>    dump and load.
> 2. Support for $FreeBSD$ - user-specified keywords are not supported
>    and won't be until after svn-1.0 by the looks of things.
> 3. Converting the repository. This is a tricky one - I tried the
>    current version of the migration scripts and they barfed and died
>    pretty quickly. Still, I'm pretty sure that the svn developers
>    are planning to fix most of those problems. From mailing-list
>    archives, it appears that they are using our cvs tree as test
>    material for the migration scripts.

Perfection (or as close as possible) of cvs2svn.py is scheduled for
1.0. They've entered beta now, but without scanning the lists I suppose
that's "sometime 2004".

I've noticed some other projects having problems with repository
conversion, but at least things seem to be getting better.

-- 
Munish Chopra