| /external/libyuv/files/ |
| D | setup_links.py | 131 def announce(self, planning): argument
151 def announce(self, planning): argument
157 if planning:
172 def announce(self, planning): argument
173 if planning:
208 def announce(self, planning): argument
209 if planning:
281 action.announce(planning=True)
288 action.announce(planning=True)
323 action.announce(planning=False)
|
| /external/angle/third_party/zlib/patches/ |
| D | 0007-zero-init-deflate-window.patch | 16 the former doesn't exist in upstream zlib, I'm not planning to send this
|
| /external/zlib/patches/ |
| D | 0007-zero-init-deflate-window.patch | 16 the former doesn't exist in upstream zlib, I'm not planning to send this
|
| /external/tensorflow/.github/ISSUE_TEMPLATE/ |
| D | 20-documentation-issue.md | 57 Are you planning to also submit a pull request to fix the issue? See the docs
|
| /external/libusb/ |
| D | README.git | 38 We also suggest that, if you are planning to bring in a large development, you
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-02-06-TypeNotationDebate.txt | 6 This is the way that I am currently planning on implementing types:
|
| /external/llvm-project/llvm/docs/HistoricalNotes/ |
| D | 2001-02-06-TypeNotationDebate.txt | 6 This is the way that I am currently planning on implementing types:
|
| /external/conscrypt/ |
| D | CONTRIBUTING.md | 27 If planning on making a large change, feel free to [create an issue on
|
| /external/libwebsockets/READMEs/ |
| D | README.release-policy.md | 13 into your planning that you will need to follow v4.0-stable in order to stay on
19 should build into your planning that you will follow lws release upgrades.
|
| /external/libcxx/utils/google-benchmark/ |
| D | CONTRIBUTING.md | 42 issue that you are planning to work on that bug or feature so that it can
|
| /external/llvm-project/libcxx/utils/google-benchmark/ |
| D | CONTRIBUTING.md | 42 issue that you are planning to work on that bug or feature so that it can
|
| /external/google-benchmark/ |
| D | CONTRIBUTING.md | 42 issue that you are planning to work on that bug or feature so that it can
|
| /external/llvm-project/llvm/utils/benchmark/ |
| D | CONTRIBUTING.md | 42 issue that you are planning to work on that bug or feature so that it can
|
| /external/llvm-project/llvm/docs/Proposals/ |
| D | VectorizationPlan.rst | 28 approach" to vectorization planning:
184 VPlan-to-VPlan algorithms. Finally, VPlan will support the planning process
204 VPlan execution time, will instead take part in the planning process by modeling
|
| D | LLVMLibC.rst | 119 llvm-libc development is still in the planning phase.
|
| /external/guice/ |
| D | CONTRIBUTING.md | 34 issue that you are planning to work on that bug or feature so that it can
|
| /external/llvm-project/clang/docs/ |
| D | Tooling.rst | 90 Examples of tools we are building or planning as part of the Clang project:
|
| /external/clang/docs/ |
| D | Tooling.rst | 90 Examples of tools we are building or planning as part of the Clang project:
|
| /external/mesa3d/docs/relnotes/ |
| D | 3.1 | 129 Keith Harrison contributed many of them. I've been planning on adding
|
| /external/grpc-grpc/src/csharp/ |
| D | README.md | 46 You only need to go through these steps if you are planning to develop gRPC C#.
|
| /external/googletest/ |
| D | README.md | 24 * We are planning to take a dependency on
|
| /external/iperf3/docs/ |
| D | 2017-04-27.txt | 79 In the near-term, we're planning another iperf3 release that will
|
| /external/catch2/docs/ |
| D | limitations.md | 91 Because C++11 provides the necessary tools to do this, we are planning
|
| /external/boringssl/src/ |
| D | BREAKING-CHANGES.md | 72 When planning a large project that depends on a breaking change, prefer to make the breaking change…
|
| /external/grpc-grpc/src/php/ |
| D | README.md | 234 planning to provide a better way to download and install the plugin
|