On May 1, 5:39 pm, Carl Meyer <[email protected]> wrote: > It's just a cron job and a local repo using hgsubversion; every five > minutes it pulls the latest from Subversion and pushes it to Bitbucket. > The repo and cron job are hosted on the djangoproject.com server. If you > are able to get the conversion from git working and repeatable on a > local repo, I think Jacob can probably get you hooked up to host it on > djangoproject.com (which also has an ssh key with permission to push to > bitbucket.org/django/django). > > The tricky bit will be making the switch to sourcing from git in a way > that doesn't change all the historical commit hashes, making the new > mirror repo merge-incompatible with the current mirror (and all clones > of it). It's possible there will be no way to do that, in which case I > guess a new incompatible mirror is still better than no mirror at all.
Okay, I'll take a look at it. In the meantime, I've pinged someone at Atlassian to see if they already have something/might be interested in hosting and maintaining a mirror (since BitBucket actually uses Django). I'll still try it out with a local repo to see how it works (as time permits). Thanks and regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
