Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Subject: Repository conversion, WAS: Re: Re[2]: [PROPOSAL] Move APR to the
	subversion repository
From: Sander Striker <striker@apache.org>
To: Lev Serebryakov <lev@serebryakov.spb.ru>
Cc: "Brian W. Fitzpatrick" <fitz@red-bean.com>, dev@apr.apache.org
In-Reply-To: <11310596443.20040313184831@serebryakov.spb.ru>
References: <1079115949.1671.134.camel@localhost.localdomain>
	 <679028524.20040312234948@serebryakov.spb.ru>
	 <1079189067.8813.7.camel@pantheon.red-bean.com>
	 <11310596443.20040313184831@serebryakov.spb.ru>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1079195622.5383.299.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Sat, 13 Mar 2004 17:33:42 +0100

First off all, the repository conversion toolset is irrelevant
to this proposal.  The repository will be converted by the
Infrastructure Team (hi fitz!), and an integrity check will
be done.  If we encounter bugs in cvs2svn during the process,
those will be fixed.

And the other way around aswell.  If cvs2svn encounters an impossible
state, it will warn, and we can fix up the CVS repository.

Furthermore, over the years people have done some wonky things
directly in the filesystem, in some ASF projects, to 'preserve
history'.  I'm willing to bet that even when checking out a tree
with CVS you may end up with a broken tree.  This is all to do
with the fact CVS tracks files and not trees.

That said it becomes a bit more apparent why we _need_ knobs to
turn and buttons to push to do a conversion tweaked to fit our
needs.

Now, given this all has very little to do with APR, it would be
best to find a different forum for any followup discussion.

Thanks,

Sander