hi guys

it's pretty straight forward if there's no bug in gc exporter ;) just click
on "export to github". current committers/owners should create github
account first. you can try and retry as needed, just remove github repo
before relaunching an export.

btw matt buildbot obviously will stop working, but there may not be much to
change, just use a git observer instead of svn, that could do the trick. as
for release process, svn export can't be used... something to work on as
well...

fwiw
cheers
s.

On Tue, Mar 17, 2015, 14:12 Matthew Schinkel <[email protected]>
wrote:

> We can't move anywhere if we don't have anyone to move our google code
> data somewhere else.
>
> Any volunteers?
>
> --
> You received this message because you are subscribed to the Google Groups
> "jallib" 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/jallib.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" 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/jallib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to