> This shows a lack of understanding about our processes Yes it does, which is why I asked about it yesterday. I'll send a webrev.
Thanks, Nir On Tue, Jan 9, 2018 at 8:50 PM, Kevin Rushforth <kevin.rushfo...@oracle.com> wrote: > Why would you even try to push a changeset without getting it reviewed > first??? > > This shows a lack of understanding about our processes and policies. Only > committers have permission to push changesets, and only after review. > Please familiarize yourself with the policies and procedures surrounding > contributing to OpenJFX [1] [2] [3] [4] [5]. Once you are familiar with > these policies and have signed the Oracle Contributor Agreement (OCA) you > can work with someone to sponsor your change. > > -- Kevin > > [1] http://openjdk.java.net/contribute/ > [2] http://www.oracle.com/technetwork/community/oca-486395.html > [3] https://wiki.openjdk.java.net/display/OpenJFX/Submitting+a+Bug+Report > [4] https://wiki.openjdk.java.net/display/OpenJFX/Code+Reviews > [5] https://wiki.openjdk.java.net/display/OpenJFX/Committing+the+Code > > > > Nir Lisker wrote: > >> Iv'e created a small documentation fix and tried to push it to >> http://hg.openjdk.java.net/openjfx/jfx-dev/rt. I got an error: >> >> abort: push creates new remote head 2152a80ee902! >> hint: pull and merge or see 'hg help push' for details about pushing new >> heads >> [command returned code 255 Tue Jan 09 19:40:10 2018] >> >> What can be the problem? >> >> >
