-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi all,
i'm currently thinking of upgrading the "pd-gem" project on sourceforge, since sf seems to want drop support for the older system on the long run (and i'd prefer to do it while i can choose when to do it).
some information on the upgrade process can be found at [1]. i think the main difference we will experience is, that the repository address will change. OLD: ssh://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem NEW: ssh://git.code.sf.net/p/pd-gem/Gem (or git:// rather than ssh:// for anonymous checkouts)
from other projects i have migrated it seems that the old repository will stay available, but they won't get automatically synched after the migration (which might to lead to some confusion until everybody uses the new URL)(btw, it seems to be possible to manually push to the old repository for now)
if somebody has objections, they should speak up,
f gamdr IOhannes
[1] https://sourceforge.net/p/upgrade/
-----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.
.hc
On 01/17/2013 10:58 AM, IOhannes m zmoelnig wrote:
hi all,
i'm currently thinking of upgrading the "pd-gem" project on sourceforge, since sf seems to want drop support for the older system on the long run (and i'd prefer to do it while i can choose when to do it).
some information on the upgrade process can be found at [1]. i think the main difference we will experience is, that the repository address will change. OLD: ssh://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem NEW: ssh://git.code.sf.net/p/pd-gem/Gem (or git:// rather than ssh:// for anonymous checkouts)
from other projects i have migrated it seems that the old repository will stay available, but they won't get automatically synched after the migration (which might to lead to some confusion until everybody uses the new URL)(btw, it seems to be possible to manually push to the old repository for now)
if somebody has objections, they should speak up,
f gamdr IOhannes
[1] https://sourceforge.net/p/upgrade/
_______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-01-17 16:58, IOhannes m zmoelnig wrote:
hi all,
i'm currently thinking of upgrading the "pd-gem" project on sourceforge, since sf seems to want drop support for the older system on the long run (and i'd prefer to do it while i can choose when to do it).
so i've initiated an upgrade of the pd-gem project *just now*.
in the meantime, i have pulled all recent changes (there aren't so many anyhow), to my github account.
fgamsdr IOhannes
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig