llvm dev - Oct 2019 - [Openmp-dev] 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

On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev
wrote:
> 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

> -Tom
> 
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
>

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

What's the github meta bug bug # ?

On Tue, Oct 22, 2019 at 12:57 PM Tom Stellard via lldb-dev <
lldb-dev at lists.llvm.org> wrote:
> On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote:
> > 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
>
>
> > -Tom
> >
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> >
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191022/e07ab2a3/attachment-0001.html>

On Tue, 2019-10-22 at 09:57 -0700, Tom Stellard via lldb-dev
wrote:
> On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote:
> > 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 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.

-- 
Best regards,
Michał Górny

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191022/d22348f1/attachment.sig>

On Tue, 2019-10-22 at 09:57 -0700, Tom Stellard via cfe-dev
wrote:
> On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote:
> > 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 at 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 at 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