| /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()
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()
1078 if (patches != NULL) in cJSONUtils_ApplyPatchesCaseSensitive()
1080 current_patch = patches->child; in cJSONUtils_ApplyPatchesCaseSensitive()
1096 static void compose_patch(cJSON * const patches, const unsigned char * const operation, const unsig… in compose_patch() argument
1100 if ((patches == NULL) || (operation == NULL) || (path == NULL)) in compose_patch()
[all …]
|
| D | cJSON_Utils.h | 44 CJSON_PUBLIC(int) cJSONUtils_ApplyPatches(cJSON * const object, const cJSON * const patches);
45 …UBLIC(int) cJSONUtils_ApplyPatchesCaseSensitive(cJSON * const object, const cJSON * const patches);
|
| /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/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/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];
|
| /third_party/libdrm/ |
| D | CONTRIBUTING.rst | 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.
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
74 - Will be regularly contributing further patches. This includes regular
102 patches that violate the documented merge criteria, will also be handled through
|
| /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
|
| D | 18.1.8.rst | 92 - cherry-ignore: Add more 18.2 only patches
94 - cherry-ignore: Add more 18.2 patches
97 - cherry-ignore: Add a couple of two fixes warning patches
98 - cherry-ignore: Add patch that needs more significant patches to
|
| /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:
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/mesa3d/docs/ |
| D | submittingpatches.rst | 11 - Code patches should follow Mesa :doc:`coding
13 - Whenever possible, patches should only affect individual Mesa/Gallium
150 It should go without saying that patches must be tested. In general, do
153 You should always run the Mesa test suite before submitting patches. The
155 pass before patches will be accepted, this may mean you have to update
163 As mentioned at the beginning, patches should be bisectable. A good way
197 If you revise your patches based on code review and push an update to
198 your branch, you should maintain a **clean** history in your patches.
199 There should not be "fixup" patches in the history. The series should be
216 - Make sure your MR is closed if your patches get pushed outside of
[all …]
|
| /third_party/skia/third_party/externals/spirv-cross/shaders-no-opt/asm/tesc/ |
| D | array-of-block-output-initializer.asm.tesc | 9 … OpEntryPoint TessellationControl %main "main" %gl_out %gl_InvocationID %_ %patches %v2 %v3 %verts
27 OpName %patches "patches"
47 OpDecorate %patches Location 2
82 %patches = OpVariable %_ptr_Output__arr_vert_patch_uint_2 Output %patches_zero
|
| /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/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/node/doc/contributing/maintaining/ |
| D | maintaining-icu.md | 123 in `tools/icu/icu-generic.gyp` or add patch files to `tools/icu/patches`.
146 > See section below about floating patches to ICU.
174 > See section below about floating patches to ICU.
199 ## Floating patches to ICU
201 Floating patches are applied at `configure` time. The "patch" files
220 mkdir -p tools/icu/patches/63
223 mkdir -p tools/icu/patches/63/source/tools/toolutil/
227 tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp
230 (edit tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp )
239 INFO: Using floating patch "tools/icu/patches/63/source/tools/toolutil/pkg_genc.cpp" from "tools/ic…
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/X86/ |
| D | README-FPStack.txt | 8 http://gcc.gnu.org/ml/gcc-patches/2004-04/msg00659.html
44 http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02410.html
55 http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02006.html
56 http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02011.html
|
| /third_party/libcoap/examples/riot/ |
| D | Makefile | 21 rm -rf pkg_libcoap/patches ; \
22 mkdir -p pkg_libcoap/patches ; \
26 (cd pkg_libcoap/patches ; git format-patch -n $${RIOT_HASH}) ; \
|
| /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
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
352 1 week for big patches) then commit your patch if you think it is OK.
[all …]
|
| /third_party/libwebsockets/READMEs/ |
| D | README.release-policy.md | 11 time these attract dozens or even hundreds of minor or major fix patches
27 subject to history rewrites, patches moving about and being squashed etc. In
35 If you have patches (you are a hero) they should be targeted at `main`.
39 patches there. Instead use a flow like this:
96 Periodically fix patches pile up on the -stable branch and are tagged out as
117 in-progress patches in-tree by updating them in place. If this doesn't make
122 with a history, like a one-way pile of patches on top of the original release. If
|
| /third_party/googletest/googletest/scripts/ |
| D | upload.py | 714 patches = dict()
715 [patches.setdefault(v, k) for k, v in patch_list]
716 for filename in patches.keys():
718 file_id_str = patches.get(filename)
1166 patches = []
1185 patches.append((filename, ''.join(diff)))
1192 patches.append((filename, ''.join(diff)))
1193 return patches
1201 patches = SplitPatch(data)
1203 for patch in patches:
[all …]
|
| /third_party/ltp/tools/sparse/sparse-src/ |
| D | .gitignore | 37 patches-*
40 patches
|
| /third_party/rust/crates/minimal-lexical/scripts/ |
| D | timings.py | 15 from matplotlib import patches
107 ax.add_patch(patches.Rectangle(
114 ax.add_patch(patches.Rectangle(
|
| /third_party/libcoap/ |
| D | CONTRIBUTE | 40 want to discuss some patches, please write it to the mailing list. Please
78 with the 'origin/develop' as parent so you can later create the patches
86 At some point you will have to generate patches to post them on the mailing
105 single patches, this will be going easy with the 'git format-patch' command
109 To not mix up your series with probably unrelated patches let git place the
110 patches within a defined directory. Also, while create the patches, tell git to
112 hold probably explanations why you create the patches in the way you have done.
119 your patches to libcoap-developers@lists.sourceforge.net
207 * A patch/commit or a series of patches/commits have to ensure that the
|
| /third_party/ltp/utils/benchmark/ebizzy-0.3/ |
| D | ChangeLog | 6 <rrbranco@br.ibm.com> for frequent patches and testing.
16 <rrbranco@br.ibm.com> for frequent patches and testing.
|
| /third_party/libnl/ |
| D | README.md | 12 The following patches is carried by the openEuler:libnl3 open source library:
16 The following patches are added to solve the compilation problem under the OpenHarmony project:
|
| /third_party/node/deps/v8/third_party/zlib/ |
| D | README.chromium | 27 - Plus the changes in 'patches' folder.
30 - Backported patches from 1.2.12 release (Work In Progress).
|