Rename BINARY to REMOTING_HOST_BINARY

Rename BINARY to REMOTING_HOST_BINARY

The current usage of BINARY as a define identifier prevents the usage of BINARY
as a constant name in a planned refactor of base::Value
(http://crrev.com/2539363004). This change addresses this issue by renaming
BINARY to a more descriptive REMOTING_HOST_BINARY.

BUG=646113
R=wez@chromium.org
CC=brettw@chromium.org

Committed: https://crrev.com/bf139498e86e7f2cc5ee1e09c63e8e71ef34918c
Cr-Commit-Position: refs/heads/master@{#436951}

[jdoerrie, 2016-12-07 08:27:38]

The CQ bit was checked by jdoerrie@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-07 08:27:51]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-07 09:39:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-07 09:39:56]

Dry run: This issue passed the CQ dry run.

[joedow, 2016-12-07 14:51:20]

joedow@chromium.org changed reviewers:
+ joedow@chromium.org

[joedow, 2016-12-07 14:51:20]

lgtm

[jdoerrie, 2016-12-07 14:52:30]

The CQ bit was checked by jdoerrie@chromium.org

[commit-bot: I haz the power, 2016-12-07 14:52:46]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-07 14:57:38]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481122350840850, "parent_rev":
"c238eee33551c43f83192352ff82261437a6c9c1", "commit_rev":
"e109608015d5f7cd49ad8c0644e9c25da710f70a"}

[commit-bot: I haz the power, 2016-12-07 14:58:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-07 15:00:05]

Description was changed from

==========
Rename BINARY to REMOTING_HOST_BINARY

The current usage of BINARY as a define identifier prevents the usage of BINARY
as a constant name in a planned refactor of base::Value
(http://crrev.com/2539363004). This change addresses this issue by renaming
BINARY to a more descriptive REMOTING_HOST_BINARY.

BUG=646113
R=wez@chromium.org
CC=brettw@chromium.org
==========

to

==========
Rename BINARY to REMOTING_HOST_BINARY

The current usage of BINARY as a define identifier prevents the usage of BINARY
as a constant name in a planned refactor of base::Value
(http://crrev.com/2539363004). This change addresses this issue by renaming
BINARY to a more descriptive REMOTING_HOST_BINARY.

BUG=646113
R=wez@chromium.org
CC=brettw@chromium.org

Committed: https://crrev.com/bf139498e86e7f2cc5ee1e09c63e8e71ef34918c
Cr-Commit-Position: refs/heads/master@{#436951}
==========

[commit-bot: I haz the power, 2016-12-07 15:00:06]

Patchset 1 (id:??) landed as
https://crrev.com/bf139498e86e7f2cc5ee1e09c63e8e71ef34918c
Cr-Commit-Position: refs/heads/master@{#436951}