Searched refs:change (Results 1 – 23 of 23) sorted by relevance
82 void addChange(Change change) { in addChange() argument84 newElement.setAttribute(XML_NAME_ATTR, change.name); in addChange()85 newElement.setAttribute(XML_ID_ATTR, change.id.toString()); in addChange()86 if (change.disabled) { in addChange()89 if (change.loggingOnly) { in addChange()92 if (change.enabledAfter != null) { in addChange()93 newElement.setAttribute(XML_ENABLED_AFTER_ATTR, change.enabledAfter.toString()); in addChange()95 if (change.description != null) { in addChange()96 newElement.setAttribute(XML_DESCRIPTION_ATTR, change.description); in addChange()99 if (change.qualifiedClass != null) { in addChange()[all …]
86 Change change = in process() local88 writer.addChange(change); in process()219 private Change verifyChange(Element element, Change change) { in verifyChange() argument220 if (change.disabled && change.enabledAfter != null) { in verifyChange()226 if (change.loggingOnly && (change.disabled || change.enabledAfter != null)) { in verifyChange()233 return change; in verifyChange()
97 CHANGE_LOG=$(mktemp --suffix srcgen-change.log)164 --change-log ${CHANGE_LOG} \
17 involved with your change. This will help determine what tests you write40 This is the code that actually runs the test. If your change76 All tests should be passing before you submit your change.109 first run the test file your code change affected individually. The139 Again, you shouldn't need to change vts10-tradefed code.
103 for change in self.tree.getroot():105 new_change.attrib = change.attrib.copy()
4 individual test from a suite can be as simple as a test config file change. One7 change to pull it out of presubmit check.
102 // [CVD only] The kernel build target: "kernel". This is unlikely to change.106 // It's very unlikely that this will ever change.
13 # that this will ever change.
6 … and amended by the 'manage_sim.py' utility. Its contents are subject to change so users are highl…
615 for change in modified_wo_commit:617 os.path.normpath('{}/{}'.format(git_path, change)))
617 for change in modified_wo_commit:619 os.path.normpath('{}/{}'.format(git_path, change)))
30 Why did we change from the historical doclava signature format (v1)40 changes. (For example, you can change the return value of a final method from43 And if we were going to change the signature format, we might as well make some231 (also applying the @interface terminology change described above) :323 is a compile-incompatible change.374 files since they're entirely implied by the enum, you can't change them, and
164 nullness, such as attempting to change a nullness contract incompatibly165 (e.g. you can change a parameter from non null to nullable for final classes,
37 classes may change any time without regard to existing clients outside of `apksig` and `apksigner`._
15 …eedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarant…19 … that you receive source code or can get it if you want it; that you can change the software and u…64 … modified to carry prominent notices stating that you changed the files and the date of any change.75 …n you can specify that version instead if you wish.) Do not make any other change in these notices.77 Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU Gen…
34 // change.
152 where shareUserId apps would like to change their signing
155 where shareUserId apps would like to change their signing
17 Note: Use this stack change to test all LE testcases:
193 * `pylint`: Alias of `pylint2`. Will change to `pylint3` by end of 2019.
248 chnage||change
META-INF/ META-INF/MANIFEST.MF jline/ jline/CompletionHandler.class CompletionHandler ...