jdk-submit is reset, please re-clone and "hg out" before push

Aleksey Shipilev shade at redhat.com
Thu Dec 13 21:40:45 UTC 2018


On 12/13/18 8:30 PM, Aleksey Shipilev wrote:
> On 12/13/18 5:15 PM, Stanislav Smirnov wrote:
>> yesterday, as some of you predicted, all the old branches were unintentionally pushed from a local clone.
>> Mistakes in this area affect everyone, unfortunately. Please be careful and pay attention.
> 
> This would happen again, until automated checks prevent it. For example, reject the push of more
> than a single branch? It is a mild inconvenience for most users who do the feature-by-feature pushes.
> 
>> It did not break the system, but to play safe the jdk-submit repository was reset. With no branches except from the default one.
>>
>> 	http://hg.openjdk.java.net/jdk/submit/ <http://hg.openjdk.java.net/jdk/submit/>
>>
>> In order to continue using the submit repo please make a fresh clone and run “hg out” before pushing to the origin.
> 
> Tarball regenerated here:
>   https://builds.shipilev.net/workspaces/jdk-sandbox.tar.xz

Oops, wrong link! Here:
   https://builds.shipilev.net/workspaces/jdk-submit.tar.xz

-Aleksey



More information about the jdk-dev mailing list