Hi, I suggest to deactivate SVN, to avoid the situation where someone still reads it, therefore getting an old state of development.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I agree. I suppose everyone actively developing knows about the switch to git, and have switched already. Keeping SVN active is only confusing, when it's not being held up to date.
I wouldn't remove it yet, just to have some backup should it turn out not everything was ported to git perfectly.
Greets,
Dieter
2010/3/14 Marc Delisle marc@infomarc.info:
Hi, I suggest to deactivate SVN, to avoid the situation where someone still reads it, therefore getting an old state of development.
Hi
Dne Sun, 14 Mar 2010 09:05:30 -0400 Marc Delisle marc@infomarc.info napsal(a):
I suggest to deactivate SVN, to avoid the situation where someone still reads it, therefore getting an old state of development.
I wanted to do that, but I haven't find way to disable advertising the repository while keeping the data in place.
Anyway I have backup of the SVN repository in case it would be needed for something, so we can probably safely remove it (I just also noticed I still have around CVS backup from time we migrated from CVS to SVN ;-)).
Michal Čihař a écrit :
Hi
Dne Sun, 14 Mar 2010 09:05:30 -0400 Marc Delisle marc@infomarc.info napsal(a):
I suggest to deactivate SVN, to avoid the situation where someone still reads it, therefore getting an old state of development.
I wanted to do that, but I haven't find way to disable advertising the repository while keeping the data in place.
It's now disabled and the data is still in place. I'm not even sure we are allowed to destroy the data, per SourceForge policy.
Anyway I have backup of the SVN repository in case it would be needed for something, so we can probably safely remove it (I just also noticed I still have around CVS backup from time we migrated from CVS to SVN ;-)).
Michal the backup guy ;)
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař