It seems this is the last report of the year (there will be more in January, though, but probably not many more ;-)), so here we are again reporting on the progress of this task... which is nearly done!
As you can check in the table at the bottom, Blink is 100%
done now, //content is at 99.81% and the other
directories altogether are at the 97.93% mark (and
these include //components/arc, which can't be migrated now - see
), so almost there! Additionally, we also landed a small update
to the PRESUBMIT.py script  so that we now raise errors when
old types are introduced in Blink and warnings everywhere else but
in //components/arc (whose migration needs to be agreed with the
folks maintaining libchrome for Android, see  again).
Last, it's worth noting that, similarly to what we did in last
report for Blink only, all numbers here now take into account the
false positives that the grep query would find, which have been
now subtracted from the numbers throughout the whole spreadsheet
also for //content and "others" now, thanks to the efforts of
Julie who did the exhaustive search needed and updated the
spreadsheet (see more details at )
Find more detail in the base spreadsheet at:
You received this message because you are subscribed to the Google Groups "chromium-mojo" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-moj...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-mojo/e2e9b885-7453-ee2c-531e-108165882b29%40igalia.com.
You received this message because you are subscribed to the Google Groups "platform-architecture-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to platform-architect...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/platform-architecture-dev/CABg10jwpo6p1tiyZE6%3D0TZKVorv%2BZ2P7kJtDj3%2BjbVAM8bmgtg%40mail.gmail.com.
Sorry for the late reply. I think we can start filing bugs blocking crbug.com/955171, if that's ok?
For now I've only filed one bug to track the issue with
//components/arc, where I wrote a summary of the discussion from
the ML at , hoping we can better get feedback from the
Android/libchrome folks that way (please feel free to add anyone
that you think might help to Cc). See it at crbug.com1035484.
Will file more bugs as they are needed, of course.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-mojo/CAHgVhZUhf5GHLp_XzShVE8HHy0DNiEeOs_6OpqFRBsaHg-QtcQ%40mail.gmail.com.