Revert "Added a ForceYouTubeRestrict policy and deprecated the old ForceYouTubeSafetyMode policy"

Revert "Added a ForceYouTubeRestrict policy and deprecated the old ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/53375

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478
Committed: https://chromium.googlesource.com/chromium/src/+/e0272627e60748462851aae327c242599066b80e

[nasko, 2016-10-06 19:51:28]

Description was changed from

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

BUG=590478
==========

to

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478
==========

[commit-bot: I haz the power, 2016-10-06 19:56:11]

Description was changed from

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478
==========

to

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478

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

[commit-bot: I haz the power, 2016-10-06 19:56:12]

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

[nasko, 2016-10-06 19:57:25]

Description was changed from

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478

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

to

==========
Revert "Added a ForceYouTubeRestrict policy and deprecated the old
ForceYouTubeSafetyMode policy"

This reverts commit c42c0dddcb3c630cb30096d16a4485bd1025eccc.

Reason:
The PolicyTest.ForceSafeSearch test is failing on Windows bots.
https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

TBR=ljusten@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=590478

Committed:
https://chromium.googlesource.com/chromium/src/+/e0272627e60748462851aae327c2...
==========

[nasko, 2016-10-06 19:57:27]

Committed patchset #1 (id:1) manually as
e0272627e60748462851aae327c242599066b80e (presubmit successful).

[Thiemo Nagel, 2016-10-17 09:40:36]

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

[Thiemo Nagel, 2016-10-17 09:40:37]

Nasko, is there a specific reason why you didn't click "Revert Patchset" on the
original CL?  Re-using the existing CL has lots of advantages: Orignal committer
and reviewers get notified automatically, also in the long run it's much easier
to track whether a CL has been reverted.

This has been re-landed in https://codereview.chromium.org/2401743003/.

[Thiemo Nagel, 2016-10-17 09:40:38]

Nasko, is there a specific reason why you didn't click "Revert Patchset" on the
original CL?  Re-using the existing CL has lots of advantages: Orignal committer
and reviewers get notified automatically, also in the long run it's much easier
to track whether a CL has been reverted.

This has been re-landed in https://codereview.chromium.org/2401743003/.

[nasko, 2016-10-17 16:56:14]

On 2016/10/17 09:40:38, Thiemo Nagel (slow) wrote:
> Nasko, is there a specific reason why you didn't click "Revert Patchset" on
the
> original CL?  Re-using the existing CL has lots of advantages: Orignal
committer
> and reviewers get notified automatically, also in the long run it's much
easier
> to track whether a CL has been reverted.

I am well aware that it is best to track through reverts directly. I don't
recall what the exact reason I had to revert it manually was, but I wouldn't
have done it if the automated way worked.

[Thiemo Nagel, 2016-10-17 17:00:09]

> I am well aware that it is best to track through reverts directly. I don't
> recall what the exact reason I had to revert it manually was, but I wouldn't
> have done it if the automated way worked.

In that case, please disregard my message. :)