Why doesn't it thrill you?
I think svn is a great tool, don't get me wrong. Very well
written and got all the features one could want. But I
don't know (or see) the actual problem you are trying to
solve. cvs seems to be wroking really well for gcc. The
weaknesses of cvs, such as the pain of renaming and
moving directories, isn't really an issue for that codebase
(at least not very often).
Maybe I am just being too conservative but for a project
as stable and vital to teh community as gcc, changing something
as fundamental as its SCM should come with a pretty big long
set of justifictions (all coolness factors waived). There's
a lot of infrastructure behind the current CVS (all the
ssh access control, integration with bugzilla, automated
mailings, all manner of things) that would need to be
updated. Its not just a matter of changing the repository
format and fixing viewcvs. I know you are aware of all of
that too, this isn't news.
So I guess I'd like to know: what is the actual problem
or problems you aim to solve by moving to svn?
then I hope that the repo will be an FSFS one and not BerkeleyDB?
Yes.
I'm a subversion developer. I'm pretty aware of the problems in BDB.
:)
I knoew your name sounded familiar :)
Kean
