cpovirk 7b8681c092 Set compatible_with on individual targets rather than use default_compatible_with. ... I'm making this change ONLY for packages with targets that I'll be removing the appengine constraint from. default_compatible_with is fine in general; I just want to separate the default_compatible_with->compatible_with CLs from the CLs that remove compatible_with. This is part of the cleanup after [] Tested: blaze build --nobuild ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=159713533		2017-07-10 11:09:26 -04:00
..
BUILD	Set compatible_with on individual targets rather than use default_compatible_with.	2017-07-10 11:09:26 -04:00
console.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
contact-settings.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
contact-us.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
dashboard.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
demo_css.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
epp.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
forms.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
kd_components.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
registrar_imports_raw.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
registry.css	Make registrar console logo non-Google-Registry-specific	2016-10-03 16:05:02 -04:00
resources.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00
security-settings.css	mv com/google/domain/registry google/registry	2016-05-13 18:55:08 -04:00