It's there.

git clone https://github.com/openjdk/loom.git

On 8/29/19, 1:47 PM, "loom-dev on behalf of Remi Forax" 
<[email protected] on behalf of [email protected]> wrote:

    Works for me,
    It's way faster at home and even in CI env (on AWS us-west), doing a clone 
get a boost from ~2m10s to ~1m10s.
    
    Rémi
    
    ----- Mail original -----
    > De: "Ron Pressler" <[email protected]>
    > À: "loom-dev" <[email protected]>
    > Envoyé: Mardi 27 Août 2019 11:16:50
    > Objet: Re: Project Loom Is Moving to GitHub
    
    > The transition is done. Project Loom is now on GitHub.
    > 
    > — R
    > 
    > 
    > 
    > On August 23, 2019 at 1:01:09 PM, Ron Pressler
    > ([email protected](mailto:[email protected])) wrote:
    > 
    >> Next week, Project Loom will transition, on a trial basis, to a Git 
repository
    >> hosted on GitHub on as part of Project Skara [1].
    >>  
    >> The GitHub Loom repository is at [2] (which is currently a read-only 
mirror).
    >>  
    >> Loom was chosen as a Skara early adopter because of the relatively small 
number
    >> of active committers, as well as the fact that most of them are in the 
European
    >> time zones, like the Skara team, who will then be able to provide close 
support.
    >>  
    >> Developers who are interested in learning more about the Skara tools and
    >> workflow
    >> can find information on the Skara Wiki [3], GitHub project [4], and 
mailing list
    >> [5].
    >>  
    >> At the moment, Project Loom will not be accepting unsolicited 
pull-requests. Any
    >> contribution from a non-committer must first be discussed on the Loom 
mailing
    >> list [6].
    >>  
    >> Ron
    >>  
    >> [1] https://openjdk.java.net/jeps/357
    >> [2] https://github.com/openjdk/loom
    >> [3] https://wiki.openjdk.java.net/display/skara
    >> [4] https://github.com/openjdk/skara
    >> [5] https://mail.openjdk.java.net/mailman/listinfo/skara-dev
    >> [6] https://mail.openjdk.java.net/mailman/listinfo/loom-dev
    >>  
    >>  
    >>  
    

Reply via email to