Home
last modified time | relevance | path

Searched full:please (Results 1 - 25 of 8335) sorted by relevance

12345678910>>...334

/third_party/backends/doc/descriptions/
H A Dkodak.desc17 :comment "Please test!"
25 :comment "Please test!"
30 :comment "Please test!"
35 :comment "Please test!"
40 :comment "Please test!"
45 :comment "Please test!"
50 :comment "Please test!"
58 :comment "Please test!"
63 :comment "Please test!"
68 :comment "Please tes
[all...]
H A Dkodakaio.desc18 :comment "Please test!"
30 :comment "Please test!"
36 :comment "Please test!"
42 :comment "Please test!"
48 :comment "Please test!"
54 :comment "Please test!"
66 :comment "Please test!"
72 :comment "Please test!"
78 :comment "Please test!"
84 :comment "Please tes
[all...]
H A Dcanon_dr.desc29 :comment "Please test!"
35 :comment "Please test!"
41 :comment "Please test!"
47 :comment "Please test!"
53 :comment "Please test!"
59 :comment "Please test!"
65 :comment "Same as CR-180? Please test!"
71 :comment "Please test!"
77 :comment "Older version? Please test!"
83 :comment "Later version? Please tes
[all...]
/third_party/typescript/tests/baselines/reference/
H A DjsxUnclosedParserRecovery.types109 ><div> <diddy bananas="please"</div> : any
112 <diddy bananas="please"
113 ><diddy bananas="please" : any
125 ><div> <diddy<boolean> bananas="please"</div> : any
128 <diddy<boolean> bananas="please"
129 ><diddy<boolean> bananas="please" : any
156 ><div> <diddy<boolean> bananas="please"/</div> : any
159 <diddy<boolean> bananas="please"/
160 ><diddy<boolean> bananas="please"/ : any
188 ><div> <diddy<boolean> bananas="please"></di
[all...]
H A DjsxUnclosedParserRecovery.js24 <diddy bananas="please"
28 <diddy<boolean> bananas="please"
36 <diddy<boolean> bananas="please"/
44 <diddy<boolean> bananas="please">
64 <diddy bananas="please"
69 <diddy<boolean> bananas="please"
79 <diddy<boolean> bananas="please"/
89 <diddy<boolean> bananas="please">
110 <diddy bananas="please"
115 <diddy<boolean> bananas="please"
[all...]
H A DjsxUnclosedParserRecovery.errors.txt78 <diddy bananas="please"
84 <diddy<boolean> bananas="please"
98 <diddy<boolean> bananas="please"/
112 <diddy<boolean> bananas="please">
152 <diddy bananas="please"
159 <diddy<boolean> bananas="please"
175 <diddy<boolean> bananas="please"/
191 <diddy<boolean> bananas="please">
226 <diddy bananas="please"
233 <diddy<boolean> bananas="please"
[all...]
H A DjsxUnclosedParserRecovery.symbols65 <diddy bananas="please"
75 <diddy<boolean> bananas="please"
93 <diddy<boolean> bananas="please"/
111 <diddy<boolean> bananas="please">
152 <diddy bananas="please"
163 <diddy<boolean> bananas="please"
183 <diddy<boolean> bananas="please"/
203 <diddy<boolean> bananas="please">
252 <diddy bananas="please"
267 <diddy<boolean> bananas="please"
[all...]
/third_party/typescript/tests/cases/conformance/jsx/
H A DjsxUnclosedParserRecovery.ts26 <diddy bananas="please"
30 <diddy<boolean> bananas="please"
38 <diddy<boolean> bananas="please"/
46 <diddy<boolean> bananas="please">
66 <diddy bananas="please"
71 <diddy<boolean> bananas="please"
81 <diddy<boolean> bananas="please"/
91 <diddy<boolean> bananas="please">
112 <diddy bananas="please"
117 <diddy<boolean> bananas="please"
[all...]
/third_party/json/docs/mkdocs/docs/integration/
H A Dpackage_managers.md61 If you are using the [Meson Build System](http://mesonbuild.com), add this source tree as a [meson subproject](https://mesonbuild.com/Subprojects.html#using-a-subproject). You may also use the `include.zip` published in this project's [Releases](https://github.com/nlohmann/json/releases) to reduce the size of the vendored source tree. Alternatively, you can get a wrap file by downloading it from [Meson WrapDB](https://wrapdb.mesonbuild.com/nlohmann_json), or simply use `meson wrap install nlohmann_json`. Please see the meson project for any issues regarding the packaging.
67 If you are using [Conan](https://www.conan.io/) to manage your dependencies, merely add `nlohmann_json/x.y.z` to your `conanfile`'s requires, where `x.y.z` is the release version you want to use. Please file issues [here](https://github.com/conan-io/conan-center-index/issues) if you experience problems with the packages.
99 If you are using [Spack](https://www.spack.io/) to manage your dependencies, you can use the [`nlohmann-json` package](https://spack.readthedocs.io/en/latest/package_list.html#nlohmann-json). Please see the [spack project](https://github.com/spack/spack) for any issues regarding the packaging.
103 If you are using [hunter](https://github.com/cpp-pm/hunter) on your project for external dependencies, then you can use the [nlohmann_json package](https://hunter.readthedocs.io/en/latest/packages/pkg/nlohmann_json.html). Please see the hunter project for any issues regarding the packaging.
107 If you are using [Buckaroo](https://buckaroo.pm), you can install this library's module with `buckaroo add github.com/buckaroo-pm/nlohmann-json`. Please file issues [here](https://github.com/buckaroo-pm/nlohmann-json). There is a demo repo [here](https://github.com/njlr/buckaroo-nholmann-json-example).
111 If you are using [vcpkg](https://github.com/Microsoft/vcpkg/) on your project for external dependencies, then you can install the [nlohmann-json package](https://github.com/Microsoft/vcpkg/tree/master/ports/nlohmann-json) with `vcpkg install nlohmann-json` and follow the then displayed descriptions. Please see the vcpkg project for any issues regarding the packaging.
150 If you are using [CocoaPods](https://cocoapods.org), you can use the library by adding pod `"nlohmann_json", '~>3.1.2'` to your podfile (see [an example](https://bitbucket.org/benman/nlohmann_json-cocoapod/src/master/)). Please file issues [here](https://bitbucket.org/benman/nlohmann_json-cocoapod/issues?status=new&status=open).
154 If you are using [NuGet](https://www.nuget.org), you can use the package [nlohmann.json](https://www.nuget.org/packages/nlohmann.json/). Please check [this extensive description](https://github.com/nlohmann/json/issues/1132#issuecomment-452250255) on how to use the package. Please file issues [here](https://github.com/hnkb/nlohmann-json-nuget/issues).
158 If you are using [conda](https://conda.io/), you can use the package [nlohmann_json](https://github.com/conda-forge/nlohmann_json-feedstock) from [conda-forge](https://conda-forge.org) executing `conda install -c conda-forge nlohmann_json`. Please fil
[all...]
/third_party/backends/doc/descriptions-external/
H A Dsamsung.desc25 :comment "Multi Function Peripheral. External backend made by Samsung. Please check the Samsung website and/or contact us if you have a Samsung device not mentioned here."
31 :comment "Please contact us if you use this device."
49 :comment "Please contact us if you use this device."
60 :comment "Please contact us if you use this device."
65 :comment "Please contact us if you use this device."
70 :comment "Please contact us if you use this device."
75 :comment "Please contact us if you use this device."
80 :comment "Please contact us if you use this device."
/third_party/node/deps/npm/tap-snapshots/test/lib/utils/
H A Derror-message.js.test.cjs369 If you believe this might be a permissions issue, please double-check the
402 If you believe this might be a permissions issue, please double-check the
435 If you believe this might be a permissions issue, please double-check the
468 If you believe this might be a permissions issue, please double-check the
501 If you believe this might be a permissions issue, please double-check the
552 To permanently fix this problem, please run:
592 To permanently fix this problem, please run:
632 To permanently fix this problem, please run:
672 If you believe this might be a permissions issue, please double-check the
706 If you believe this might be a permissions issue, please doubl
[all...]
/third_party/skia/third_party/externals/angle2/scripts/
H A Dangle_presubmit_utils_unittest.py55 "Commit 1:Please ensure that your" +
78 "Commit 1:Please ensure that there are tags (e.g., Bug:, Test:) in your description."
88 "Commit 1:Please ensure that there are tags (e.g., Bug:, Test:) in your description."
99 "Commit 1:Please ensure the summary is only 1 line and there is 1 blank line" + \
166 "Commit 1:Please ensure that your description summary is on one line of 64 or less characters."
181 "Commit 1:Please ensure that there exists only 1 blank line between tags and description body."
187 Please wrap it to 72 characters. Lines without spaces or lines starting with 4 spaces are exempt."""
273 Please wrap it to 72 characters. Lines without spaces or lines starting with 4 spaces are exempt."""
279 Please wrap it to 72 characters. Lines without spaces or lines starting with 4 spaces are exempt."""
300 Please wra
[all...]
/third_party/glfw/docs/
H A DCONTRIBUTING.md30 forum. Please don't open a GitHub issue to discuss design questions without
78 If your bug is already reported, please add any new information you have, or if
100 Please also include the __complete build log__ from your compiler and linker,
121 Please also include any __error messages__ provided to your application via the
152 Please verify that context creation also fails with the `glfwinfo` tool before
162 If you are running your program in a virtual machine, please mention this and
165 Please also include the __GLFW version string__ (`3.2.0 X11 EGL clock_gettime
204 If you are running your program in a virtual machine, please mention this and
207 Please also include any __error messages__ provided to your application via the
244 If you are running your program in a virtual machine, please mentio
[all...]
/third_party/typescript/
H A DSECURITY.md7 If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
11 **Please do not report security vulnerabilities through public GitHub issues.**
13 Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
15 If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
17 You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
19 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
31 If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.
/third_party/tzdata/
H A DCONTRIBUTING3 Please do not create issues or pull requests on GitHub, as the
11 free to fill gaps or fix mistakes, and please email improvements
12 to <tz@iana.org> for use in the future. In your email, please give
17 To email small changes, please run a POSIX shell command like
22 such as renaming, adding or removing zones, please read
31 For changes that fix sensitive security-related bugs, please see the
34 Please submit changes against either the latest release
/third_party/icu/icu4j/main/tests/core/src/com/ibm/icu/dev/test/message2/
H A DCustomFormatterMessageRefTest.java110 .setPattern("{Please start {$browser :msgRef gcase=genitive resbundle=$res}}") in test()
114 .setPattern("{Please start {$browser :msgRef resbundle=$res}}") in test()
118 assertEquals("cust-grammar", "Please start Firefoxin", mf1.formatToString(arguments)); in test()
119 assertEquals("cust-grammar", "Please start Firefox", mf2.formatToString(arguments)); in test()
122 assertEquals("cust-grammar", "Please start Chromen", mf1.formatToString(arguments)); in test()
123 assertEquals("cust-grammar", "Please start Chrome", mf2.formatToString(arguments)); in test()
126 assertEquals("cust-grammar", "Please start Safarin", mf1.formatToString(arguments)); in test()
127 assertEquals("cust-grammar", "Please start Safari", mf2.formatToString(arguments)); in test()
/third_party/node/deps/openssl/openssl/
H A DCONTRIBUTING.md4 Please visit our [Getting Started] page for other ideas about how to contribute.
13 please open an [issue on GitHub](https://github.com/openssl/openssl/issues).
15 To submit a patch or implement a new feature, please open a
22 To make it easier to review and accept your pull request, please follow these
82 either be added to an existing test, or completely new. Please see
86 documentation. Please look at the `.pod` files in `doc/man[1357]` for
95 Please note that this is NOT simply a copy of git-log one-liners.
102 security fixes, please add a line in [NEWS.md](NEWS.md).
/third_party/openssl/
H A DCONTRIBUTING.md4 Please visit our [Getting Started] page for other ideas about how to contribute.
12 To request new features or report bugs, please open an issue on GitHub
14 To submit a patch, please open a pull request on GitHub. If you are thinking
19 To make it easier to review and accept your pull request, please follow these
66 either be added to an existing test, or completely new. Please see
70 documentation. Please look at the "pod" files in doc/man[1357] for
79 Please note that this is NOT simply a copy of git-log one-liners.
86 security fixes, please add a line in [NEWS.md](NEWS.md).
/third_party/rust/crates/rustc-hash/
H A DCODE_OF_CONDUCT.md10 * On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.
11 * Please be kind and courteous. There's no need to be mean or rude.
13 * Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
14 * We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the <a href="http://citizencodeofconduct.org/">Citizen Code of Conduct</a>; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups.
15 * Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Rust moderation team][mod_team] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back.
21 These are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Rust moderation team][mod_team].
29 7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed.
36 The enforcement policies listed above apply to all official Rust venues; including official IRC channels (#rust, #rust-internals, #rust-tools, #rust-libs, #rustc, #rust-beginners, #rust-docs, #rust-community, #rust-lang, and #cargo); GitHub repositories under rust-lang, rust-lang-nursery, and rust-lang-deprecated; and all forums under rust-lang.org (users.rust-lang.org, internals.rust-lang.org). For other projects adopting the Rust Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion.
/third_party/rust/crates/nom/.github/
H A DPULL_REQUEST_TEMPLATE.md4 First, please note that, for family reasons, I have limited time to work on
13 Please provide the following information with this pull request:
18 - if adding a new combinator, please add code documentation and some unit tests
19 in the same file. Also, please update the [combinator list](https://github.com/Geal/nom/blob/main/doc/choosing_a_combinator.md)
26 Please avoid cosmetic fixes unrelated to the pull request. Keeping the changes
32 (which might have changed while you were working on your PR), please
/third_party/skia/third_party/externals/angle2/
H A DPRESUBMIT.py106 "Please ensure that there are tags (e.g., Bug:, Test:) in your description."))
110 "Please ensure that there exists 1 blank line " +
118 commit_tag + 'Please ensure that there exists only 1 blank line '
125 'Please ensure that your description summary'
138 commit_tag + "Please ensure that your description summary is on one line of " +
146 'Please ensure the summary is only 1 line and '
156 'Please ensure that there exists only 1 blank line '
173 ' is too long.\n' + '"' + line + '"\n' + 'Please wrap it to ' +
185 output_api.PresubmitError('Please ensure that your description contains:\n'
231 long_text='Please ensur
[all...]
/third_party/rust/crates/bindgen/bindgen/
H A Dfeatures.rs90 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_0 => 1.0;
93 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_17 => 1.17;
96 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_19 => 1.19;
99 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_20 => 1.20;
102 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_21 => 1.21;
105 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_25 => 1.25;
108 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_26 => 1.26;
111 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_27 => 1.27;
114 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please report it at https://github.com/rust-lang/rust-bindgen/issues"] => Stable_1_28 => 1.28;
118 #[deprecated = "This rust target is deprecated. If you have a good reason to use this target please repor
[all...]
/third_party/mbedtls/
H A DBUGS.md7 If you think you've found a bug in Mbed TLS, please follow these steps:
15 data leak), please report it confidentially as described in
17 4. Please [create an issue on on GitHub](https://github.com/Mbed-TLS/mbedtls/issues).
19 Please do not use GitHub for support questions. If you want to know
20 how to do something with Mbed TLS, please see [`SUPPORT.md`](SUPPORT.md) for available documentation and support channels.
/third_party/mbedtls/.github/
H A Dpull_request_template.md3 Please write a few sentences describing the overall goals of the pull request's commits.
9 Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")
19 Please refer to the [contributing guidelines](https://github.com/Mbed-TLS/mbedtls/blob/development/CONTRIBUTING.md), especially the
24 - please structure your PR into a series of small commits, each of which does one thing
26 - please do not force-push to update your PR - just add new commit(s)
/third_party/backends/doc/
H A Dbackend-writing.txt27 is not already mentioned in one of the .desc files, please contact the
86 the ChangeLogs/ directory. Please note that we skipped 1.0.26.
217 * A backend library is always only one file (libsane-backendname.so). Please do
233 * Please follow the GNU coding standards. It's clear that the style
246 * Please be courteous to programmer's with terminals that are 80
247 characters wide. It's not difficult to avoid long lines, so please
256 * Please do not depend on compiler specific features or, if you do, make
304 * Please use sanei functions whenever possible (e.g.
326 * Please do not assume that `size_t' is `unsigned int'. On some
336 * Please d
[all...]

Completed in 20 milliseconds

12345678910>>...334