GitHub Migration Starting Now

Hi,

We're getting ready to start migrating to GitHub. SVN will be moved to read-only now and we'll
begin the process of turning on GitHub commit access. I'll send an email when we're done.

-Tom

Hi,

We're getting ready to start migrating to GitHub. SVN will be moved to read-only now and we'll
begin the process of turning on GitHub commit access. I'll send an email when we're done.

The migration is complete now. If you have been added as a collaborator to the llvm-project
repo, you should be able to commit directly to git now. The git-svn script is optional and should
continue to work, but you will need to supply a github user token in order to commit.

I still need to update the github collaborates from the list in SVN, so if
you have added your name in the last few days, you may not have commit access for a few more hours.

If you run into any issues, please file a bug and mark it as a blocker for the github meta-bug.

Thanks,
Tom

I’m unable to push. I filed https://bugs.llvm.org/show_bug.cgi?id=43761

What’s the github meta bug bug # ?

Looks like it’s http://llvm.org/PR39393

If I haven't added myself, should I still do that (presuming the file
can be committed to), or is there another process for getting commit
access? In case you can grant if offhand, my username is mgorny.

> Hi,
>
> We're getting ready to start migrating to GitHub. SVN will be
> moved to read-only now and we'll
> begin the process of turning on GitHub commit access. I'll send an
> email when we're done.
>

The migration is complete now.

Did everyone stop commiting or is there something strange going on? The
last commit I see is d052a578de from 8 hours ago.

Another question:

The build bot console

http://lab.llvm.org:8011/console

is now sorted on git commit id which makes it a bit hard to use atm. Is
there an issue for doing something about that?

Thanks,
Mikael

  If you have been added as a collaborator to the llvm-project
repo, you should be able to commit directly to git now. The git-svn
script is optional and should
continue to work, but you will need to supply a github user token in
order to commit.

I still need to update the github collaborates from the list in SVN,
so if
you have added your name in the last few days, you may not have
commit access for a few more hours.

If you run into any issues, please file a bug and mark it as a
blocker for the github meta-bug.

Thanks,
Tom

> -Tom
>
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev@lists.llvm.org
>

https://protect2.fireeye.com/v1/url?k=50544e46-0c8045f8-50540edd-86742d02e7e2-96dccc982e4dd0fc&q=1&e=1c901fd6-5221-4af3-a0ab-4a124a098487&u=https%3A%2F%2Flists.llvm.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fopenmp-dev

>

_______________________________________________
cfe-dev mailing list
cfe-dev@lists.llvm.org

https://protect2.fireeye.com/v1/url?k=a2f27696-fe267d28-a2f2360d-86742d02e7e2-ee8f0271cf8b963f&q=1&e=1c901fd6-5221-4af3-a0ab-4a124a098487&u=https%3A%2F%2Flists.llvm.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fcfe-dev

It looks like the meta repo is indeed read-only now. I emailed Tom
directly requesting to be added but haven't heard back yet; I suspect
there's a lot occupying his attention at the moment.

Hi,

We're getting ready to start migrating to GitHub. SVN will be
moved to read-only now and we'll
begin the process of turning on GitHub commit access. I'll send an
email when we're done.

The migration is complete now.

Did everyone stop commiting or is there something strange going on? The
last commit I see is d052a578de from 8 hours ago.

Another question:

The build bot console

http://lab.llvm.org:8011/console

is now sorted on git commit id which makes it a bit hard to use atm. Is
there an issue for doing something about that?

Can you file a bug for this?

-Tom

Thanks for reporting that, Mikael!

The sorting on the console page has been fixed. It is time based now.

Galina

I submitted bug 43790 to track this specific issue (developers who did
not manage to update github-usernames.txt prior to SVN being switched
to read-only), as it's a small finite set and is distinct from the
need for new documentation on the process by which new users will
obtain GitHub access (bug 43778).