Remove obselete entries from tools/gritsettings/resource_ids

Remove obselete entries from tools/gritsettings/resource_ids

Committed: https://crrev.com/db0550a37ec4b8e3170233671d864169ec655464
Cr-Commit-Position: refs/heads/master@{#415111}

[Lei Zhang, 2016-08-29 20:35:10]

The CQ bit was checked by thestig@chromium.org to run a CQ dry run

[Lei Zhang, 2016-08-29 20:37:15]

thestig@chromium.org changed reviewers:
+ sky@chromium.org, vitalybuka@chromium.org

[Lei Zhang, 2016-08-29 20:37:16]

sky: ash
vitalybuka: cloud_print - if someone wants to try to build these targets again,
they can set up their own resource_ids that does not conflict with the rest of
Chromium, right?

[Vitaly Buka corp, 2016-08-29 20:44:25]

On 2016/08/29 20:37:16, Lei Zhang wrote:
> sky: ash
> vitalybuka: cloud_print - if someone wants to try to build these targets
again,
> they can set up their own resource_ids that does not conflict with the rest of
> Chromium, right?

not sure what are you asking.
What is the plan? Are we going to return CP code back into chromium or move
somewhere outside?

[Lei Zhang, 2016-08-29 20:52:24]

On 2016/08/29 20:44:25, Vitaly Buka corp wrote:
> On 2016/08/29 20:37:16, Lei Zhang wrote:
> > sky: ash
> > vitalybuka: cloud_print - if someone wants to try to build these targets
> again,
> > they can set up their own resource_ids that does not conflict with the rest
of
> > Chromium, right?
> 
> not sure what are you asking.
> What is the plan? Are we going to return CP code back into chromium or move
> somewhere outside?

I don't know where the CP code has been moved to. The copy I'm working with is
just the deleted copy that has been reverted.

As is, the .grd files references here do not exist, so shouldn't they be
removed? If we put the CP code back, then we put back the .grd references here
too.

[Vitaly Buka (NO REVIEWS), 2016-08-29 21:07:52]

On 2016/08/29 20:52:24, Lei Zhang wrote:
> On 2016/08/29 20:44:25, Vitaly Buka corp wrote:
> > On 2016/08/29 20:37:16, Lei Zhang wrote:
> > > sky: ash
> > > vitalybuka: cloud_print - if someone wants to try to build these targets
> > again,
> > > they can set up their own resource_ids that does not conflict with the
rest
> of
> > > Chromium, right?
> > 
> > not sure what are you asking.
> > What is the plan? Are we going to return CP code back into chromium or move
> > somewhere outside?
> 
> I don't know where the CP code has been moved to. The copy I'm working with is
> just the deleted copy that has been reverted.
> 
> As is, the .grd files references here do not exist, so shouldn't they be
> removed? If we put the CP code back, then we put back the .grd references here
> too.

I see, I thought decision was already made.
LGTM

[commit-bot: I haz the power, 2016-08-29 21:27:17]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[sky, 2016-08-29 21:46:31]

Removal of ash/mus LGTM - thanks for cleaning up!

[commit-bot: I haz the power, 2016-08-30 03:42:36]

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

[commit-bot: I haz the power, 2016-08-30 03:42:36]

Dry run: This issue passed the CQ dry run.

[Lei Zhang, 2016-08-30 04:18:49]

The CQ bit was checked by thestig@chromium.org

[commit-bot: I haz the power, 2016-08-30 04:26:35]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-30 04:44:37]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-30 04:46:23]

Description was changed from

==========
Remove obselete entries from tools/gritsettings/resource_ids
==========

to

==========
Remove obselete entries from tools/gritsettings/resource_ids

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

[commit-bot: I haz the power, 2016-08-30 04:46:24]

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