cl/191678404

crrev.com/i/602393

M67 branch is this week. Is CL in comment 2 ready to submit? Or does this need to be handed off to the next owner (stk@)?

The CL is ready to submit, but I need to run the git5 script to pull the new files in from the p4_depot_paths CL in comment 1

pkl-macbookpro3:src(merge1) pkl$ git push origin merge1:master
Counting objects: 1019, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (546/546), done.
Writing objects: 100% (1019/1019), 176.32 KiB | 19.59 MiB/s, done.
Total 1019 (delta 458), reused 843 (delta 307)
remote: Resolving deltas: 100% (458/458)           
remote: Counting objects: 1019, done        
remote: Replicating objects... done        
remote: Processing changes: done            
To sso://bling-internal/piper.git
   e9cc6110c8..627c82218c  merge1 -> master

Submitted: https://critique.corp.google.com/#review/192235109

Updating crrev.com/i/602393 to include the new changes; I'll CQ when it's ready.

Additional files from piper were required to fix the roll, and have been added to our p4_depot_paths here: cl/192347022

crrev.com/i/602393 will be updated once again to include these new files once that CL lands.

Thank you for doing this. Feel free to hang this over to me whenever you want to, it's my shift! :) 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/ios_internal.git/+/00c643240013c6a9cc79bd3659ddbe10ac8f8b1c

commit 00c643240013c6a9cc79bd3659ddbe10ac8f8b1c
Author: Kurt Horimoto <kkhorimoto@google.com>
Date: Wed Apr 11 18:59:06 2018