Make CLD data source default value actually overridable.

Make CLD data source default value actually overridable.

Silly oversight in initial checkin, this makes the default value overridable
so that other distributions can override it if they wish without having to
change common.gypi.

BUG=367239
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279963

[Andrew Hayden (chromium.org), 2014-06-26 06:31:32]

The CQ bit was checked by andrewhayden@chromium.org

[commit-bot: I haz the power, 2014-06-26 06:32:36]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/andrewhayden@chromium.org/345223006/1

[commit-bot: I haz the power, 2014-06-26 06:45:29]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/21808)
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/25695)

[commit-bot: I haz the power, 2014-06-26 06:50:54]

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

[commit-bot: I haz the power, 2014-06-26 06:50:55]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/21810)

[Takashi Toyoshima, 2014-06-26 07:23:52]

lgtm.
you may want to write NOTRY=TRUE line in your change description.

[Takashi Toyoshima, 2014-06-26 07:26:07]

ah, but you should rebase the Patch Set 1 to apply the diff.

[Andrew Hayden (chromium.org), 2014-06-26 08:32:20]

On 2014/06/26 07:26:07, Takashi Toyoshima (chromium) wrote:
> ah, but you should rebase the Patch Set 1 to apply the diff.

Thanks! Conflict resolved, serves me right for submitting patches too frequently
:)

Thanks! I've removed you from TBR, and added NOTRY.

[Andrew Hayden (chromium.org), 2014-06-26 08:32:28]

The CQ bit was checked by andrewhayden@chromium.org

[commit-bot: I haz the power, 2014-06-26 08:33:49]

CQ is trying da patch. Follow status at

https://chromium-status.appspot.com/cq/andrewhayden@chromium.org/345223006/20001

[commit-bot: I haz the power, 2014-06-26 08:35:05]

Change committed as 279963