[MLton] Subversion

[Adam Goode]

--=-laZ9yL8RAdFz3JU64F5X
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I had good luck with cvs2svn, but only after getting all the options
correct. Specifically, without the --no-default-eol option, cvs2svn was
corrupting binary files upon import from an old CVS repository. It's
important to check things over a bit and have a few trial runs.

There are also problems importing from a repository where branches and
tags are used inconsistently. But it seems that if you've never used the
same name for both a branch and a tag, you're ok.

All in all, I'm happy with the migration. It's very nice to have
accurate history and logs.

See also: http://svn.haxx.se/dev/archive-2004-11/0745.shtml (Case study:
Mono switches to Subversion)


Thanks,

Adam


On Tue, 2005-07-26 at 10:59 -0700, Stephen Weeks wrote:
> > I would like to suggest considering migration from CVS to SVN.
>=20
> I've been thinking of making the same suggestion for a while.
>=20
> > I have been using SVN for some time on my own (small) projects and
> > the experience has been positive.
>=20
> I've been using SVN for the last 4-5 months on a largish project and
> have been quite happy.
>=20
> > Now that the so called FSFS repositories are the default, the most
> > annoying SVN repository maintenance issues are probably gone.
>=20
> Yeah, the database helped to clinch my decision not to switch to SVN
> when I looked at it last year.
>=20
> > For me, the killer features of SVN are:
> > [0. similarity to CVS; SVN is easy to learn,]
> >  1. the ability to do (among other things) status queries and diffs
> >     while not connected, and
> >  2. ability to move files and directories.
>=20
> I second these.  The speed from using local pristine copies is also
> nice.  Finally, I've found the integrated log useful -- no need to
> maintain a separate "commitlog".
>=20
> The (potential) drawback for the MLton project would be losing old
> revisions and tags.  I haven't played around with the SVN tools for
> migrating CVS repositories, but I was less than enthused about their
> accuracy after reading the documentation.  I'd be interested to hear
> others' experiences here.  The right way to go might be to simply
> freeze the CVS and start with a fresh import into the SVN.  We can
> leave the CVS server up for read access for as long as we feel it's
> useful to look at old stuff.
>=20
> Another issue is timing of the migration.  I was thinking to move
> immediately after the next release, which will hopefully be in a month
> or two.  However, Matthew and I are about to start a branch for the
> 64-bit port, so it might be better to move to SVN ASAP.
>=20
> _______________________________________________
> MLton mailing list
> MLton@mlton.org
> http://mlton.org/mailman/listinfo/mlton

--=-laZ9yL8RAdFz3JU64F5X
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBC5n0ulenB4PQRJawRAvoqAKDEfhNOKOIcwJJSuNEsPL39APDl8ACgm7/g
m8PbZg7MRl3GPFT8QGUu24M=
=T2yn
-----END PGP SIGNATURE-----

--=-laZ9yL8RAdFz3JU64F5X--