| Index: chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
|
| diff --git a/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc b/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
|
| index e33c21b43754956d9aa1bc4c2acbfad00a5ca236..6f96a85fb3f3a8e8590e90dca3094bc991520ca3 100644
|
| --- a/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
|
| +++ b/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
|
| @@ -69,10 +69,6 @@ const char* PnaclArch() {
|
| }
|
|
|
| // If we don't have Pnacl installed, this is the version we claim.
|
| -// TODO(jvoung): Is there a way to trick the configurator to ping the server
|
| -// earlier if there are components that are not yet installed (version 0.0.0.0),
|
| -// So that they will be available ASAP? Be careful not to hurt startup speed.
|
| -// Make kNullVersion part of ComponentUpdater in that case, to avoid skew?
|
| const char kNullVersion[] = "0.0.0.0";
|
|
|
| // Pnacl components have the version encoded in the path itself:
|
|
|