On 01/17/2013 18:45, Hans-Christoph Steiner wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Sounds like a good idea, it can alwso serve s a trial run for the big pure-data upgrade.
yes probably.
i have to admit though, that i was experiencing trouble with upgrades of an svn-based project.
at least with [1], the upgrade never really finished, and the migrated SVN-repository was incomplete (the 2500 revisions from the original repository ended up as 535 revisions). i'm not sure what the cause of this is, but i'm under the impression that the import is still running (though i started in october!). it might be the case that i forgot some trigger to really start the migration.
also keep in mind that it is very simple to sync multiple git repositories (e.g. the one before the migration and the one after the migration), which is a nice feature for slowly migrating the devs to the new system. afaict, migrating the svn repository involves a change of the UUID, which means that you cannot do a simple"svn relocate".
otoh, what i really like is that you can now have multiple svn-repositories per project (not sure how we can use that for pure-data; but all those GB of external libraries found in /sources could be moved into a separate repository.
sf provides tools for moving an existing svn repository: simply give it an URL to a public repo, and it will check out all of the commits. this however is rather slow, as it will spend time checking out empty commits if you direct it to a subdirectory of an existing repo (and you will get all that meaningless history for commits outside of your subdirectory).
fgmsdr IOhannes