woohoo! this is great, good luck Adrian
Brendan Smith, IT Specialist National Priorities Project http://www.nationalpriorities.org http://www.facebook.com/nationalpriorities 413 584 9556 On Apr 27, 2012, at 12:50 PM, Adrian Holovaty wrote: > Hey guys, here's an important heads-up! > > We're going to do the migration to GitHub today. This means we'll no > longer be committing code to our Subversion repository. Committers, > please hold off on making commits until the migration is done. > > I expect it'll be done by late afternoon Chicago time. I'm going to do > a dry run first to make sure all goes well, then I'll do the real > thing. > > Here are some random notes about the process -- > > * Any fork of the existing GitHub repository at > https://github.com/django/django (which was a mirror of Subversion) > will be broken. That is, it will no longer be able to get changes from > upstream. Unfortunately, there's no way around this. But we'll provide > some instructions here on django-developers on how to change your > forks to use the new upstream repository in such a way that any of > your local changes will be preserved. Worst case, you'll just have to > generate a patch of your local branch's changes and apply it to a new > fork. > > * One interesting part of this is coming up with a definitive mapping > between our old Subversion usernames and names/emails for Git. Brian > Rosner and some other folks have done a great job of doing that > research -- > https://github.com/brosner/django-git-authors/blob/master/authors.txt > -- and we'll be using that file to convert committer data during the > migration. Basically this means that if you've ever committed to > Django, your commits will be associated with your current GitHub > account -- as long as your GitHub account is associated with the same > email address in that authors file. Due to the way Git works, there's > no way of changing this data after the import is done. But we've > accounted for everybody except two mysterious people "dcf" and "cell," > both of whom were given temporary commit bits during a sprint six > years ago. > > * If you're a Git/GitHub expert and are interested in helping, feel > free to join us in #django-dev on Freenode. > > * Thanks in advance for bearing with us during this process. There > will be some pain, but it'll be worth it in the long run. I'm excited! > > Adrian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
