adb_chrome_public_command_line should write to old and new paths

build/android/adb_chrome_public_command_line

Index: build/android/adb_chrome_public_command_line
diff --git a/build/android/adb_chrome_public_command_line b/build/android/adb_chrome_public_command_line
index ac379e8f7852f53c0c366b158b353deaba5f49c0..913c21b956aaca395a189097c29e89923e3774a1 100755
--- a/build/android/adb_chrome_public_command_line
+++ b/build/android/adb_chrome_public_command_line
@@ -13,5 +13,11 @@
 # To remove all Chrome flags, pass an empty string for the flags:
 #   adb_chrome_public_command_line ""
 
+# The command line arguments file is transitioning from
+# /data/local/chrome-command-line to /data/local/tmp/chrome-command-line
+# (https://crbug.com/593720). To support both old and new builds of
+# Chrome, we currently write the same flags to both places.
+$(dirname $0)/adb_command_line.py --device-path \

[jbudorick, 2016/08/31 15:10:23]

Should this be exec $(dirname $0)/adb_command_line.py like the line below?

[johnme, 2016/08/31 17:41:46]

No, exec is an optimisation that causes bash to stop executing the current
script and replace its process with the process being run (instead of forking).
So if we exec here, we'll never run the line below.

[jbudorick, 2016/09/03 00:33:55]

I'm betraying my limited knowledge of bash, it seems. sgtm.

+    /data/local/tmp/chrome-command-line "$@" &&
 exec $(dirname $0)/adb_command_line.py --device-path \
     /data/local/chrome-command-line "$@"