Move all files related to tracked preferences from c/b/prefs to c/b/prefs/tracked.

Move all files related to tracked preferences from c/b/prefs to c/b/prefs/tracked.

This is a long-standing task, I have been waiting to proceed with it to avoid complicated merges while things were hot on the settings protection front.

Now is a good time to clean this up before doing further cleanup work.

TBR=grt@chromium.org
BUG=419505
Committed: https://crrev.com/7a1a0bc9cb0bb2c441f415fd4db6310258d0c018
Cr-Commit-Position: refs/heads/master@{#297811}

[gab, 2014-10-01 20:13:37]

Patchset #1 (id:1) has been deleted

[gab, 2014-10-01 20:13:45]

Patchset #1 (id:1) has been deleted

[gab, 2014-10-01 20:21:10]

gab@chromium.org changed reviewers:
+ bauerb@chromium.org

[gab, 2014-10-01 20:21:11]

Finally getting around to doing this which you originally requested a while
back. Now is a good time since M37 is effectively out of commission and M38/M39
have very little settings hardening modifications so the need for a merge
upstream is now unlikely.

In that some line of thought I'm about to do some cleanup work and thus want to
get this move done first such that any future change comes after it.

Cheers!
Gab

PS: I'm torn regarding ProfilePrefStoreManager which I think is effectively the
boundary; it uses a ton of tracked pref stuff, but it's more using/configuring
it than "being" it (e.g., just like chrome_pref_service_factory.cc) so I think
it belongs in c/b/prefs. LMK what you think!

[gab, 2014-10-01 20:48:42]

On 2014/10/01 20:21:11, gab wrote:
> Finally getting around to doing this which you originally requested a while
> back. Now is a good time since M37 is effectively out of commission and
M38/M39
> have very little settings hardening modifications so the need for a merge
> upstream is now unlikely.
> 
> In that some line of thought I'm about to do some cleanup work and thus want
to
> get this move done first such that any future change comes after it.
> 
> Cheers!
> Gab
> 
> PS: I'm torn regarding ProfilePrefStoreManager which I think is effectively
the
> boundary; it uses a ton of tracked pref stuff, but it's more using/configuring
> it than "being" it (e.g., just like chrome_pref_service_factory.cc) so I think
> it belongs in c/b/prefs. LMK what you think!

Also, please CQ if this LGTYs, thanks!

[Bernhard Bauer, 2014-10-02 06:36:08]

LGTM, thanks!

I agree about PrefStoreManager; it's the entry point for the tracked prefs code,
but not directly part of it.

[Bernhard Bauer, 2014-10-02 06:36:12]

The CQ bit was checked by bauerb@chromium.org

[commit-bot: I haz the power, 2014-10-02 06:36:20]

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

[commit-bot: I haz the power, 2014-10-02 06:45:40]

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

[commit-bot: I haz the power, 2014-10-02 06:45:41]

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

[gab, 2014-10-02 11:53:30]

gab@chromium.org changed reviewers:
+ grt@chromium.org

[gab, 2014-10-02 11:56:10]

TBR grt for trivial side effects in incident_reporting/

[gab, 2014-10-02 11:56:24]

The CQ bit was checked by gab@chromium.org

[commit-bot: I haz the power, 2014-10-02 11:57:12]

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

[commit-bot: I haz the power, 2014-10-02 12:03:13]

Committed patchset #1 (id:20001) as 1031f19ac2c805fcb9937f920a3ca38ecbb257cf

[commit-bot: I haz the power, 2014-10-02 12:03:52]

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