Searched refs:Changes (Results 1 – 25 of 52) sorted by relevance
123
10 * Changes should be made in all instances. */
11 * Changes should be made in all instances. */
71 Changes will not be announced.177 - Changes to the API header file178 - Changes to the API implementation(s)179 - Changes to the relevant API documentation180 - Changes to Device Tree source and bindings185 - An entry in the "API Changes" section of the release notes for the next215 Deprecation and removal of APIs will be announced in the "API Changes"234 - Include the deprecation in the "API Changes" of the release notes for the
51 Changes to APIs in the future will require adapting the version following the
50 class Changes: class117 ) -> Changes:141 return Changes(vnds=sorted(vnds_set),408 def print_changes(self, changes: Changes): argument
24 API Changes
75 Changes that require the user to modify their own application to support the new
10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are62 - Changes should not be merged before the minimal time has expired.106 Changes that appear to have an impact to the overall security of the system need112 Changes that introduce new features or functionality or change the way the143 Reviewers shall not 'Request Changes' without comments or justification286 - Changes/Updates/Additions to existing :ref:`features <feature-tracking>`.
32 Changes submitted to a collaboration branch can evolve and improve
10 Changes to existing features that are not considered a bug and would not
71 Large Changes80 Changes which require an RFC proposal include:133 - Changes to APIs must increment the API version number according to the API302 - When using the "Request Changes" option, mark trivial, non-functional,309 "Request Changes" option is used. Requested changes shall be in the scope of
