| /third_party/mesa3d/docs/ |
| D | submittingpatches.rst | 1 Submitting Patches
9 - Patches should not mix code changes with code formatting changes
11 - Code patches should follow Mesa :doc:`coding
13 - Whenever possible, patches should only affect individual Mesa/Gallium
15 - Patches should never introduce build breaks and should be bisectable
17 - Patches should be properly :ref:`formatted <formatting>`.
18 - Patches should be sufficiently :ref:`tested <testing>` before
20 - Patches should be :ref:`submitted <submit>` via a merge request for
147 Testing Patches
150 It should go without saying that patches must be tested. In general, do
[all …]
|
| /third_party/flutter/engine/flutter/web_sdk/ |
| D | libraries.yaml | 35 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/internal_patch.dart"
57 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart"
61 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/collection_patch.dart"
65 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/convert_patch.dart"
69 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart"
73 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/developer_patch.dart"
77 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/io_patch.dart"
82 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/isolate_patch.dart"
87 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/mirrors_patch.dart"
92 patches: "../../third_party/dart/sdk/lib/_internal/js_dev_runtime/patch/math_patch.dart"
[all …]
|
| D | libraries.json | 7 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/async_patch.dart", string
14 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/mirrors_patch_cfe.dart", string
22 "patches": "io_patch.dart", string
27 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/internal_patch.dart", string
67 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/core_patch.dart", string
71 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/collection_patch.dart", string
78 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/typed_data_patch.dart", string
88 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/isolate_patch.dart", string
93 "patches": "../dart-sdk/lib/_internal/js_runtime/lib/developer_patch.dart", string
103 "patches": "../dart-sdk/lib/js/_js_client.dart", string
[all …]
|
| /third_party/flutter/skia/third_party/externals/icu/ |
| D | README.chromium | 19 2. Review and apply patches/changes in "D. Local Modifications" if
20 necessary/applicable. Update patch files in patches/.
156 b. Drop local patches we used to have for the following issues. They'll
170 1. Applied locale data patches from Google obtained by diff'ing
173 - patches/locale_google.patch:
181 - patches/locale1.patch: Minor fixes for Korean
184 2. Breakiterator patches
185 - patches/wordbrk.patch for word.txt
191 - patches/khmer-dictbe.patch
197 patch: patches/cjdict.patch
[all …]
|
| /third_party/libdrm/ |
| D | CONTRIBUTING.rst | 4 Submitting Patches
7 Patches should be sent to dri-devel@lists.freedesktop.org, using git
8 send-email. For patches only touching driver specific code one of the driver
15 libdrm" to make it easier to find libdrm patches. This is best done by running
31 Your patches should also include a Signed-off-by line with your name and email
41 We won't reject patches that lack S-o-b, but it is strongly recommended.
46 Patches should have at least one positive review (Reviewed-by: tag) or
64 spelling fixes and whitespace adjustment) patches that have been merged
66 drivers, merged patches to those components also count towards the commit
71 peoples patches but just make sure that patch submission isn't one-way
[all …]
|
| /third_party/skia/third_party/externals/icu/ |
| D | README.chromium | 20 2. Review and apply patches/changes in "D. Local Modifications" if
21 necessary/applicable. Update patch files in patches/.
146 b. Drop local patches we used to have for the following issues. They'll
157 1. Applied locale data patches from Google obtained by diff'ing
160 - patches/locale_google.patch:
168 - patches/locale1.patch: Minor fixes for Korean
171 2. Breakiterator patches
172 - patches/wordbrk.patch for word.txt
178 - patches/khmer-dictbe.patch
184 patch: patches/cjdict.patch
[all …]
|
| /third_party/libsnd/ |
| D | CONTRIBUTING.md | 14 ## Submitting Patches
16 * Patches should pass all existing tests
17 * Patches should pass all pre-commit hook tests.
18 * Patches should always be submitted via a either Github "pull request" or a
19 via emailed patches created using "git format-patch".
20 * Patches for new features should include tests and documentation.
21 * Patches to fix bugs should either pass all tests, or modify the tests in some
|
| /third_party/elfutils/ |
| D | CONTRIBUTING | 6 The developer mailinglist to send patches to is
13 Please supply patches using git format-patch or using git send-email.
18 procedure for patches based on the procedure used by the Linux kernel
73 at least a handful of accepted patches and agree to the guidelines in
74 this document for creating, reviewing, accepting and committing patches.
81 committers can push patches through:
87 Patches should also be posted to the mailinglist.
89 As a maintainer/committer you should still post patches as described
97 patches on these branches are works in progress, so might not be perfect
100 the same process as above should be followed by posting the patches
|
| /third_party/ffmpeg/doc/ |
| D | developer.texi | 23 best way to proceed is to send your patches to the ffmpeg-devel
35 @item Submitting patches to the ffmpeg-devel mailing list.
36 See @ref{Submitting patches} for details.
144 accept patches to remove their use unless they absolutely do not impair
256 @section Patches/Committing
257 @subheading Licenses for patches must be compatible with FFmpeg.
308 the way we do. Send your changes as patches to the ffmpeg-devel mailing
312 @subheading Cosmetic changes should be kept in separate patches.
344 @subheading Complex patches should refer to discussion surrounding them.
345 When applying patches that have been discussed (at length) on the mailing
[all …]
|
| /third_party/node/doc/guides/ |
| D | maintaining-icu.md | 114 in `tools/icu/icu-generic.gyp` or add patch files to `tools/icu/patches`.
137 > See section below about floating patches to ICU.
166 > See section below about floating patches to ICU.
196 ## Floating patches to ICU
198 Floating patches are applied at `configure` time. The "patch" files
202 Patches are tied to a specific ICU version. They won’t apply to a
217 mkdir -p tools/icu/patches/63
220 mkdir -p tools/icu/patches/63/source/tools/toolutil/
224 tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp
227 (edit tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp )
[all …]
|
| /third_party/icu/vendor/double-conversion/ |
| D | UPDATING.md | 30 …patches on double-conversion (diff between the ICU4C source tree and the vendor source tree), then…
44 …p directory. If you want to keep the temp directory to refer to the ICU patches, for example, you…
46 ## Checking ICU Patches
48 …any ICU patches in the icu4c/i18n version of the code files; they should be marked clearly with "I…
|
| /third_party/cef/tools/ |
| D | patcher.py | 33 patch_path = os.path.join(cef_patch_dir, 'patches', patch_file + '.patch')
59 patches = scope["patches"]
63 for patch in patches:
83 sys.stdout.write('\n%d patches total (%d applied, %d skipped, %d failed)\n' % \
84 (len(patches), results['apply'], results['skip'], results['fail']))
89 '%d patches failed to apply. Your build will not be correct.' %
|
| /third_party/flutter/engine/flutter/lib/snapshot/ |
| D | libraries.yaml | 21 patches:
30 patches:
38 patches:
44 patches: "../../../third_party/dart/runtime/lib/convert_patch.dart"
48 patches:
82 patches:
89 patches:
99 patches:
117 patches:
123 patches: "../../../third_party/dart/runtime/lib/math_patch.dart"
[all …]
|
| D | libraries.json | 10 "patches": [ array
45 "patches": [ array
54 "patches": [ array
61 "patches": [ array
69 "patches": "../../../third_party/dart/runtime/lib/typed_data_patch.dart", string
76 "patches": [ array
84 "patches": [ array
91 "patches": [ array
102 "patches": [ array
121 "patches": [ array
[all …]
|
| /third_party/vk-gl-cts/scripts/verify/ |
| D | package.py | 34 …def __init__ (self, basePath, statement, testLogs, gitStatus, gitLog, patches, summary, conformVer… argument
40 self.patches = patches
52 patches = []
69 patches.append(item)
76 …return PackageDescription(packagePath, statement, testLogs, gitStatus, gitLog, patches, summary, c…
|
| /third_party/cJSON/ |
| D | cJSON_Utils.c | 1038 CJSON_PUBLIC(int) cJSONUtils_ApplyPatches(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatches() argument
1043 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatches()
1045 /* malformed patches. */ in cJSONUtils_ApplyPatches()
1049 if (patches != NULL) in cJSONUtils_ApplyPatches()
1051 current_patch = patches->child; in cJSONUtils_ApplyPatches()
1067 …PUBLIC(int) cJSONUtils_ApplyPatchesCaseSensitive(cJSON * const object, const cJSON * const patches) in cJSONUtils_ApplyPatchesCaseSensitive() argument
1072 if (!cJSON_IsArray(patches)) in cJSONUtils_ApplyPatchesCaseSensitive()
1074 /* malformed patches. */ in cJSONUtils_ApplyPatchesCaseSensitive()
1078 if (patches != NULL) in cJSONUtils_ApplyPatchesCaseSensitive()
1080 current_patch = patches->child; in cJSONUtils_ApplyPatchesCaseSensitive()
[all …]
|
| /third_party/libcoap/ |
| D | CONTRIBUTE | 39 want to discuss some patches, please write it to the mailing list. Please
73 with the 'origin/develop' as parent so you can later create the patches
80 At some point you will have to generate patches to post them on the mailing
86 single patches, this will be going easy with the 'git format-patch' command
89 To not mix up your series with probably unrelated patches let git place the
90 patches within a defined directory. Also, while create the patches, tell git to
92 hold probably explanations why you create the patches in the way you have done.
99 your patches to libcoap-developers@lists.sourceforge.net
161 5.5 Patches and Commits
170 * A patch/commit or a series of patches/commits have to ensure that the
|
| /third_party/skia/third_party/externals/angle2/third_party/r8/ |
| D | README.chromium | 23 * Refer to commit descriptions within "3pp/patches" directory.
54 * Apply patches:
56 git am $CHROMIUM_SRC/third_party/r8/patches/*.patch
58 * Save new patches. Change number if expecting more or fewer patches:
59 git format-patch -3 -o $CHROMIUM_SRC/third_party/r8/3pp/patches
60 * Submit these fixed patches and the bot will automatically retry.
|
| /third_party/gstreamer/gstreamer/ |
| D | README.static-linking | 75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch
|
| /third_party/gstreamer/gstplugins_base/ |
| D | README.static-linking | 75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch
|
| /third_party/gstreamer/gstplugins_good/ |
| D | README.static-linking | 75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch
|
| /third_party/gstreamer/gstplugins_bad/ |
| D | README.static-linking | 75 style patches against a GStreamer release or a snapshot of a GStreamer git
76 repository. The patches should ideally say what was changed and why it
77 was changed, and there should ideally be separate patches for independent
158 patches/glib/glib.patch
159 patches/gst-plugins-bad/gst-plugins-bad.patch
160 patches/gst-plugins-base/gst-plugins-base.patch
161 patches/gst-plugins-good/gst-plugins-good.patch
162 patches/gstreamer/gstreamer.patch
163 patches/openssl/openssl.patch
|
| /third_party/mesa3d/docs/relnotes/ |
| D | 18.1.7.rst | 59 - cherry-ignore: Add additional 18.2 only patches
60 - cherry-ignore: Add more 18.2 patches
61 - cherry-ignore: Add more 18.2 patches
62 - cherry-ignore: Add a couple of patches with > 1 fixes tags
63 - cherry-ignore: more 18.2 patches
|
| /third_party/ltp/tools/sparse/sparse-src/Documentation/ |
| D | submitting-patches.md | 1 Submitting patches
5 [Submitting Patches](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html)
18 …Sign your work](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#sign-your-wo…
|
| /third_party/skia/third_party/externals/spirv-cross/reference/shaders-no-opt/asm/tesc/ |
| D | array-of-block-output-initializer.asm.tesc | 22 } patches[2];
59 patches[0].v2 = _6_0_init[0];
63 patches[1].v2 = _6_0_init[1];
67 patches[0].v3 = _6_1_init[0];
71 patches[1].v3 = _6_1_init[1];
|