Moving to SubVersion

Tobias Koenig tokoe at
Fri Oct 8 21:28:05 BST 2004

On Fri, Oct 08, 2004 at 07:40:30PM +0000, Frans Englich wrote:
> On Friday 08 October 2004 19:19, Charles Samuels wrote:

> Yes, there lies sense in that; I read somewhere(I can obviously not find the 
> link now) a discussion of various version control systems and the conclusion 
> was nothing particular, but it clearly showed subversion isn't the obvious 
> choice. But one shouldn't go blind on technical features; aspects like user 
> base and market share makes a big difference too, especially in the long 
> run(for example, who care about the "perfect" system when no one uses it).
We want to have a versioning system that is familiar to all developers,
and since svn has nearly the same commands like cvs, that's the perfect
solution for us.

> KDE switching version control system would be one of the biggest of its kind, 
> and have a large impact, so it's important it's done properly. The ones who 
> is interested in the switch, should do a thorough investigation, collect 
> references, our demands, disassemble every option to the bone -- from license 
> to barf capabilities -- and write a paper.
... and in 5 years we can start switching...

Hell, we are developer and we want a working system, not officialism...

How to migrate?

1) Disconnect for one hour
2) Make a copy of the cvs repository
3) Run csv2svn over the copy
4) Test the svn repository by checking it out and run a diff over
   the cvs and the svn checkout
5) Check if the branches were converted correctly (this might take the most time)
6) Move the svn repository back to
7) Put online

All good things count 7, so nothing can goes wrong.

Separate politics from religion and economy!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <>

More information about the kde-core-devel mailing list