Standardize usage of virtual/override/final in chrome/browser/task_manager/

Standardize usage of virtual/override/final in chrome/browser/task_manager/

This patch was automatically generated by applying clang fixit hints
generated by the plugin to the source tree.

BUG=417463
TBR=nick@chromium.org

Committed: https://crrev.com/1ca8a7c75b0eb927301d4168722637b7235c41a6
Cr-Commit-Position: refs/heads/master@{#300464}

[dcheng, 2014-10-21 10:06:33]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-10-21 10:08:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/663023009/1

[commit-bot: I haz the power, 2014-10-21 11:08:53]

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

[commit-bot: I haz the power, 2014-10-21 11:08:54]

Try jobs failed on following builders:
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[dcheng, 2014-10-21 11:12:07]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-10-21 11:15:58]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/663023009/1

[commit-bot: I haz the power, 2014-10-21 11:52:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-21 11:53:09]

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

[ncarter (slow), 2014-10-21 14:57:02]

lgtm

[ncarter (slow), 2014-10-21 14:58:29]

Is this an appropriate use of TBR? It's a mechanical change, but do we
really want to be committing code without review?

On Tue, Oct 21, 2014 at 4:53 AM, <commit-bot@chromium.org> wrote:

> Patchset 1 (id:??) landed as
> https://crrev.com/1ca8a7c75b0eb927301d4168722637b7235c41a6
> Cr-Commit-Position: refs/heads/master@{#300464}
>
> https://codereview.chromium.org/663023009/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[dcheng, 2014-10-21 15:42:26]

On 2014/10/21 at 14:58:29, nick wrote:
> Is this an appropriate use of TBR? It's a mechanical change, but do we
> really want to be committing code without review?
> 
> On Tue, Oct 21, 2014 at 4:53 AM, <commit-bot@chromium.org> wrote:
> 
> > Patchset 1 (id:??) landed as
> > https://crrev.com/1ca8a7c75b0eb927301d4168722637b7235c41a6
> > Cr-Commit-Position: refs/heads/master@{#300464}
> >
> > https://codereview.chromium.org/663023009/
> >
> 
> To unsubscribe from this group and stop receiving emails from it, send an
email to chromium-reviews+unsubscribe@chromium.org.
> 

I did explicitly mention that this was my plan on chromium-dev, and no one
objected. But I don't feel strongly about it either way.