| /external/clang/test/Sema/ |
| D | attr-deprecated-message.c | 4 typedef int INT1 __attribute__((deprecated("Please avoid INT1"))); // expected-note 3 {{'INT1' has …
6 typedef INT1 INT2 __attribute__ ((__deprecated__("Please avoid INT2")));
8 typedef INT1 INT1a; // expected-warning {{'INT1' is deprecated: Please avoid INT1}}
10 typedef INT1 INT1b __attribute__ ((deprecated("Please avoid INT1b")));
12 INT1 should_be_unavailable; // expected-warning {{'INT1' is deprecated: Please avoid INT1}}
15 INT1 f1(void) __attribute__ ((deprecated("Please avoid f1"))); // expected-note {{'f1' has been exp…
16 INT1 f2(void); // expected-warning {{'INT1' is deprecated: Please avoid INT1}}
18 typedef enum {red, green, blue} Color __attribute__((deprecated("Please avoid Color"))); // expecte…
21 Color c1; // expected-warning {{'Color' is deprecated: Please avoid Color}}
24 int g2 __attribute__ ((deprecated("Please avoid g2"))); // expected-note {{'g2' has been explicitly…
[all …]
|
| /external/tlsdate/ |
| D | HACKING.md | 1 Please feel free to contribute patches; here are the basic guidelines to hack
4 Please work from a git tree by cloning the repo:
8 Please file bugs on the tlsdate issue tracker:
12 Please use the github pull request feature when possible.
45 tlsdate is security sensitive - please consider where you add code and in
88 Please provide relevant CHANGELOG entries for all changes.
89 Please remove items from the TODO file as they are completed.
90 Please provide unittest cases.
92 When submitting patches via email, please use `git format-patch` to format
99 When applying patches, please use `git am` to apply patches:
[all …]
|
| /external/autotest/docs/ |
| D | coding-style.md | 4 but please stick to the rules anyway ;-)
9 Please use Python where possible. It's not the ideal language for everything,
58 of your variable_names please. I shall make a bedgrudging exception for class
128 nontrivial function. When creating docstrings, please add a newline at the
130 the docstring has multiple lines, please include a short summary line followed
131 by a blank line before continuing with the rest of the description. Please
186 Please keep functions short, under 30 lines or so if possible. Even though
201 Please don't raise string exceptions, as they're deprecated and will be removed
203 you will raise, please look at http://docs.python.org/lib/module-exceptions.html
215 attatch them, I don't care much. Please base them off the current version.
|
| /external/chromium-trace/catapult/third_party/gsutil/gslib/addlhelp/ |
| D | support.py | 24 please first read the `FAQ <https://developers.google.com/storage/docs/faq>`_.
26 If you still have questions please use one of the following methods as
30 please search for and post questions on Stack Overflow, using the official
37 Cloud Console, or other administration-related questions please email
40 To help us diagnose any issues you encounter, please provide these details
58 If you make any local modifications to gsutil, please make sure to use
66 For questions about billing or account issues, please visit
|
| D | dev.py | 27 hurdles. Please fill out either the individual or corporate Contributor
84 8. Please make sure to run all tests against your modified code. To
97 If you made changes to boto, please run the boto tests. For these tests you
116 9. Please consider contributing test code for your change, especially if the
119 10. When it's time to send us code, please use the Rietveld code review tool
|
| /external/autotest/client/site_tests/bluetooth_RegressionClient/ |
| D | bluetooth_RegressionClient.py | 61 self.tell_user('Please disconnect all Bluetooth devices using (x).')
72 self.tell_user('Please turn off all Bluetooth devices.<br>'
78 self.check_working(message='Please turn devices back on and connect.')
83 self.tell_user('Please unpair all Bluetooth devices (using (x))')
89 self.check_working(message='Please re-pair and connect devices.')
94 self.tell_user('Please disable Bluetooth (uncheck Enable Bluetooth).')
100 self.tell_user('Please enable Bluetooth (check Enable Bluetooth).<br>'
|
| /external/icu/icu4c/source/tools/tzcode/ |
| D | tzselect.ksh | 73 echo >&2 'Please identify a location' \
83 echo >&2 'Please select a continent or ocean.'
100 echo >&2 'Please enter a number in range.';;
115 echo >&2 'Please enter the desired value' \
164 echo >&2 'Please select a country.'
168 '') echo >&2 'Please enter a number in range.';;
202 echo >&2 'Please select one of the following' \
207 '') echo >&2 'Please enter a number in range.';;
284 '') echo >&2 'Please enter 1 for Yes, or 2 for No.';;
|
| /external/dagger2/ |
| D | CONTRIBUTING.md | 7 When submitting code, please make every effort to follow existing conventions
10 Where appropriate, please provide unit tests or integration tests. Unit tests
18 Please make sure your code compiles by running `mvn clean verify` which will
25 please ensure that the form is consistent with the existing files, and please
|
| /external/clang/www/analyzer/ |
| D | filing_bugs.html | 19 We also welcome feature requests. When filing a bug report, please do the
30 <li>Test cases don't tell us everything. Please briefly describe the problem you
40 <p>Please <a href="http://llvm.org/bugs/enter_bug.cgi?product=clang">file
47 (e.g., preview versions of SDKs or seed releases of Mac OS X) please file bug
57 <p>Please file bugs in Radar against the <b>clang - static analyzer</b> component.</p>
|
| /external/icu/icu4j/main/classes/core/src/com/ibm/icu/util/ |
| D | SimpleTimeZone.java | 111 * day-of-week-in-month. Please see the member
113 * @param startDayOfWeek The daylight savings starting day-of-week. Please
116 * time, which is standard time in this case. Please see the
121 * Please see the member description for an example.
122 * @param endDayOfWeek The daylight savings ending day-of-week. Please
125 * which is daylight time in this case. Please see the
155 * day-of-week-in-month. Please see the member
157 * @param startDayOfWeek The daylight savings starting day-of-week. Please
160 * time, which is standard time in this case. Please see the
166 * Please see the member description for an example.
[all …]
|
| /external/icu/android_icu4j/src/main/java/android/icu/util/ |
| D | SimpleTimeZone.java | 108 * day-of-week-in-month. Please see the member
110 * @param startDayOfWeek The daylight savings starting day-of-week. Please
113 * time, which is standard time in this case. Please see the
118 * Please see the member description for an example.
119 * @param endDayOfWeek The daylight savings ending day-of-week. Please
122 * which is daylight time in this case. Please see the
151 * day-of-week-in-month. Please see the member
153 * @param startDayOfWeek The daylight savings starting day-of-week. Please
156 * time, which is standard time in this case. Please see the
162 * Please see the member description for an example.
[all …]
|
| /external/webrtc/webrtc/build/sanitizers/ |
| D | lsan_suppressions_webrtc.cc | 13 // LSAN_OPTIONS=suppressions=/path/to/suppressions. Please refer to
18 // Please make sure the code below declares a single string variable
26 // Chromium. Please don't add new entries here unless they're present in there.
45 // PLEASE DO NOT ADD SUPPRESSIONS FOR NEW LEAKS.
107 // PLEASE READ ABOVE BEFORE ADDING NEW SUPPRESSIONS.
110 ; // Please keep this semicolon.
|
| /external/mockito/src/org/mockito/ |
| D | Answers.java | 30 …* <p>Please see the {@link org.mockito.Mockito#RETURNS_DEFAULTS} documentation for more details.</…
39 …* <p>Please see the {@link org.mockito.Mockito#RETURNS_SMART_NULLS} documentation for more details…
48 … * <p>Please see the {@link org.mockito.Mockito#RETURNS_MOCKS} documentation for more details.</p>
58 …* <p>Please see the {@link org.mockito.Mockito#RETURNS_DEEP_STUBS} documentation for more details.…
67 …* <p>Please see the {@link org.mockito.Mockito#CALLS_REAL_METHODS} documentation for more details.…
|
| /external/llvm/docs/ |
| D | ReleaseNotes.rst | 24 release, please check out the `main LLVM web site <http://llvm.org/>`_. If you
31 one. To see the release notes for a specific release, please see the `releases
41 in the 3.9 release. Please migrate to using CMake. For more information see:
45 3.9 release. Please migrate to LLVMLinkModules2. Unlike the old function the
54 They will be removed in 3.9. Please migrate to the versions with a 2 suffix.
145 If you have any questions or comments about LLVM, please feel free to contact
|
| D | DeveloperPolicy.rst | 71 Please be aware that all public LLVM mailing lists are public and archived, and
85 how to check out SVN trunk, please see the `Getting Started
97 script, please separate out those changes into a separate patch from the rest
111 *For Thunderbird users:* Before submitting a patch, please open *Preferences >
119 When submitting patches, please do not add confidentiality or non-disclosure
220 burden on all developers. Please keep them short.
317 * If the patch fixes a bug in bugzilla, please include the PR# in the message.
340 quality patches. If you would like commit access, please send an email to
359 please do a test commit (e.g. change a comment or add a blank line). Your first
471 If you are interested in making a large change, and this scares you, please make
[all …]
|
| /external/chromium-trace/catapult/third_party/flot/ |
| D | CONTRIBUTING.md | 9 behavior but are not 100% certain that it is a bug, please try posting to the
12 reporting a bug, please include a working demonstration of the problem, if
18 love to hear them! Please submit each suggestion as a separate new issue.
20 If you would like to work on an existing issue, please make sure it is not
27 To make merging as easy as possible, please keep these rules in mind:
|
| /external/ceres-solver/internal/ceres/ |
| D | reorder_program.cc | 67 << "This is a Ceres bug; please contact the developers!"; in MinParameterBlock()
82 << "Please report this error to the developers."; in OrderingForSparseNormalCholeskyUsingSuiteSparse()
115 << "Please report this error to the developers."; in OrderingForSparseNormalCholeskyUsingCXSparse()
185 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
209 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
215 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
235 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
245 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
251 << "Congratulations, you found a Ceres bug! Please report this error " in LexicographicallyOrderResidualBlocks()
328 << "Congratulations, you found a Ceres bug! Please report this error " in ReorderProgramForSchurTypeLinearSolver()
|
| /external/curl/docs/ |
| D | MAIL-ETIQUETTE | 27 2.8 Please Tell Us How You Solved The Problem!
39 please use the one or the ones that suit you the most.
170 Please do not reply to an existing message as a short-cut to post a message
190 Please use a subject of the mail that makes sense and that is related to the
225 Please switch off those HTML encoded messages. You can mail all those funny
250 2.8 Please Tell Us How You Solved The Problem!
255 If you are the one who asks, please consider responding once more in case
|
| /external/avahi/docs/ |
| D | HACKING | 1 Please comply with the following rules when hacking on Avahi:
30 Please note that valgrind can't find you all bugs. Please check
35 python script please add this legal blurb to its header:
|
| /external/clang/test/Misc/ |
| D | diag-verify.cpp | 22 x = y; // expected-error{{please don't use of undeclared identifier 'y'}} in test()
23 x = y; // expected-error{{use of undeclared identifier 'y'; please declare y before use}} in test()
34 //CHECK: Line 22: please don't use of undeclared identifier 'y'
35 //CHECK: Line 23: use of undeclared identifier 'y'; please declare y before use
|
| /external/avahi/avahi-common/ |
| D | defs.h | 60 * Please note that these compatibility layers are incomplete and
78 * avahi-ui. For the other APIs please consult the original
81 * Please note that the doxygen-generated API documentation of the
85 * or because they are considered obsolete. Please consult the C header
86 * files for all definitions that are part of the Avahi API. Please
143 * avahi_alternative_service_name()) and commit again. Please do not
147 * or the port number), use the AVAHI_PUBLISH_UPDATE flag. Please do
151 * AVAHI_PUBLISH_UPDATE. Please note that you cannot use
164 * browsing domains. Please note that not all domains whith services
|
| /external/valgrind/none/tests/s390x/ |
| D | op_exception.stderr.exp | 12 you are not sure, please let us know and we'll try to fix it.
25 you are not sure, please let us know and we'll try to fix it.
38 you are not sure, please let us know and we'll try to fix it.
51 you are not sure, please let us know and we'll try to fix it.
|
| /external/libpng/contrib/arm-neon/ |
| D | README | 66 png-mng-implement@sourceforge.net. Please write code in strict C90 C where
72 Please try to make the contribution a single file and give the file a clear and
78 "BUG REPORTS" entry or both. Please make sure that the header of the file
81 Please list the OS requirements as precisely as possible. Ideally you should
|
| /external/google-breakpad/src/testing/ |
| D | README | 31 Please see the project page above for more information as well as the
33 also an IRC channel on OFTC (irc.oftc.net) #gtest available. Please
36 Please note that code under scripts/generator/ is from the cppclean
51 an internal dependency. Please read
264 If you want to use Boost's TR1 tuple library with Google Mock, please
278 Please see file ${GTEST_DIR}/README for how to tweak them.
298 may need to tweak your compiler and/or linker flags. Please see the
354 We welcome patches. Please read the Google Mock developer's guide [4]
|
| /external/gmock/ |
| D | README | 31 Please see the project page above for more information as well as the
33 also an IRC channel on OFTC (irc.oftc.net) #gtest available. Please
36 Please note that code under scripts/generator/ is from the cppclean
51 an internal dependency. Please read
272 If you want to use Boost's TR1 tuple library with Google Mock, please
286 Please see file ${GTEST_DIR}/README for how to tweak them.
306 may need to tweak your compiler and/or linker flags. Please see the
362 We welcome patches. Please read the Google Mock developer's guide [4]
|