Just make sure the project is https://github.com/los-cocos/cocos (there were other two transitory sites)
claudio On Thu, May 8, 2014 at 9:57 AM, Michał Jaworski <[email protected]> wrote: > Oh, I just saw repo on github so there was no question :P > > W dniu czwartek, 8 maja 2014 14:55:41 UTC+2 użytkownik Michał Jaworski > napisał: > >> Claudio, what's the status of migration? I have some fixes to tilemap >> collision detection and can't wait to contribute. >> >> W dniu piątek, 25 kwietnia 2014 11:14:46 UTC+2 użytkownik Michał Jaworski >> napisał: >>> >>> Ok, great :D So I remove my repository to avoid confusion. >>> >>> W dniu piątek, 25 kwietnia 2014 02:58:24 UTC+2 użytkownik Claudio Canepa >>> napisał: >>>> >>>> >>>> >>>> >>>> On Thu, Apr 24, 2014 at 8:23 PM, Michał Jaworski <[email protected]>wrote: >>>> >>>>> It seems that there there are no objections and everyone agrees with >>>>> the idea of migrating to DVCS. I've created new git repository on GitHub. >>>>> I >>>>> couldn't find neither Richard nor Claudio on GitHub so I wasn't able to >>>>> convert svn authors to git format. I think that this still isn't such a >>>>> big >>>>> loss. >>>>> >>>>> I'm not sure who should own this repo but if you tell me and give me >>>>> user/organization name on GitHub I can transfer ownership of repository. >>>>> >>>>> url of new repository: >>>>> https://github.com/swistakm/cocos2d >>>>> >>>>> >>>> hmm. >>>> I appreciate you took the work to do that, but you caught me in the >>>> middle of the migration. >>>> >>>> Done >>>> Code migration >>>> ---------------------- >>>> + migrated svn to git in my local machine >>>> + prune very old branchs >>>> + check equality between svn and git last revision and tagged >>>> revisions >>>> + upload to a testmigration project in Github >>>> + code migration is fine, I'm ready to upload to real project >>>> >>>> Issues Migration: forked a project to do issue migration and >>>> ------------------------ >>>> + Added script to produce a conversion table between svn revision >>>> and git hash, uses the stdout output of the git to svn conversion >>>> + Added code to store locally the googlecode issues, with an >>>> editable version of comments >>>> + Manual edition of local editable gcode issues to unify references >>>> to svn commits to the form r<revnum> >>>> + Scrip to change the editable version by 'r<revnum>' -> 'commit >>>> <sha>' >>>> >>>> Working now: >>>> reintegrate the gihub upload with the gcode handlers (near done) >>>> implement 'allow to specify a range of issues to upload' (near done) >>>> >>>> After that, what needs to be done is upload small chunks of issues, see >>>> how they look, massage the code as needed, iterate. >>>> I suspect that here some markdown escaping may be needed, don't know if >>>> any more. >>>> And then upload to the final project. >>>> >>>> Anyway, good-looking or not the migration should end in a very few >>>> days, I will be busy after that. >>>> >>>> >>>> >>>> >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "cocos2d discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/cocos-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cocos-discuss. For more options, visit https://groups.google.com/d/optout.
