Home
last modified time | relevance | path

Searched +full:pull +full:- +full:requests (Results 1 – 25 of 314) sorted by relevance

12345678910>>...13

/third_party/grpc/
DCONTRIBUTING_STEPS.md1 # Contributing to gRPC: A Step-By-Step Guide
10 …[active GitHub account](https://docs.github.com/en/get-started/quickstart/creating-an-account-on-g…
11 1. [An understanding of Git and GitHub](https://docs.github.com/en/get-started/using-git/about-git)
13 resolve, push, pull, fetch
14 etc.](https://docs.github.com/en/get-started/using-git/about-git)
15 1. [git installed and working on your machine](https://github.com/git-guides/install-git)
17 Objective-C, PHP, or C#.
21 The GitHub repository for the C-based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
30 [own fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-f…
33 … ![Screenshot of creating fork using a non-google account.](doc/images/img/grpc-create-fork.png)
[all …]
/third_party/rust/crates/nix/
DCONTRIBUTING.md9 [conduct]: https://www.rust-lang.org/conduct.html
16 [issues]: https://github.com/nix-rust/nix/issues
22 issues][issue-search] to see if there's something related. If not, just
23 [open a new issue][new-issue]!
29 [issue-search]: https://github.com/nix-rust/nix/search?utf8=%E2%9C%93&q=is%3Aissue&type=Issues
30 [new-issue]: https://github.com/nix-rust/nix/issues/new
33 ## Feature / API requests
36 issue][new-issue] requesting it. As with reporting a bug, the more
43 [Rust's issue labeling scheme][rust-labels]:
44 - **A-** prefixed labels state which area of the project the issue
[all …]
/third_party/vulkan-loader/
DGOVERNANCE.md5 - Alignment with the Vulkan Specification and the Loader Specification
6 - [Vulkan Specification](https://github.com/KhronosGroup/Vulkan-Docs)
7 - [Loader Specification](loader/LoaderAndLayerInterface.md)
8 - IHV/ISV Enablement
9 - Updates of loader functionality should be available in a timely fashion
10 - Every effort will be made to be responsive to IHV/ISV issues with the loader
11 - Cross Platform Compatibility
12 - LunarG: Monitor for desktop (Windows and Linux)
13 …- Continuous Integration: HW test farms operated by LunarG monitor various hardware/software platf…
14 - Repo Quality
[all …]
DCONTRIBUTING.md8 * [KhronosGroup/Vulkan-Loader](https://github.com/KhronosGroup/Vulkan-Loader)
14 * Examine the [issues list](https://github.com/KhronosGroup/Vulkan-Loader/issues)
37 GitHub under Issues and Pull Requests.
38 * Use the existing GitHub forking and pull request process.
40 [forking the repository](https://help.github.com/articles/fork-a-repo/),
42 [submitting a pull request](https://help.github.com/articles/using-pull-requests/).
44 [guidelines](#coding-conventions-and-formatting) enumerated below.
50 * The resulting Pull Request will be assigned to a repository maintainer.
51 It is the maintainer's responsibility to ensure the Pull Request
53 Once the Pull Request has been approved and is passing internal CI,
[all …]
/third_party/protobuf/
DCONTRIBUTING.md31 We accept patches in the form of github pull requests. If you are new to
32 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
43 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
45 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
50 Before sending out your pull request, please familiarize yourself with the
56 Most pull requests should go to the main branch and the change will be
59 already merged to main, and then create a pull request cherry-picking the
62 For each pull request, a protobuf team member will be assigned to review the
63 pull request. For minor cleanups, the pull request may be merged right away
66 our response time within 7-days but if you don’t get any response in a few
[all …]
/third_party/skia/third_party/externals/oboe/apps/fxlab/
DCONTRIBUTING.md9 use GitHub pull requests for this purpose. Consult
10 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
11 information on using pull requests.
/third_party/skia/m133/third_party/externals/wuffs/docs/
Dcontributing.md21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
/third_party/skia/third_party/externals/wuffs/docs/
Dcontributing.md21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
/third_party/skia/third_party/externals/swiftshader/third_party/marl/
DCONTRIBUTING.md21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
/third_party/vk-gl-cts/external/amber/src/
DCONTRIBUTING.md21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
/third_party/curl/docs/
DCONTRIBUTE.md1 <!--
4 SPDX-License-Identifier: curl
5 -->
28 notified of pull requests and new issues posted there.
60 [curl-library mailing list](https://curl.se/mail/list.cgi?list=curl-library)
69 [CODE_STYLE](https://curl.se/dev/code-style.html) already established in
75 ### Non-clobbering All Over
87 odd problems, but discussions and opinions do not agree with 510 of them - or
104 the most up-to-date sources from the git repository, but the latest release
136 Ideally you file a [pull request on
[all …]
/third_party/libphonenumber/
DCONTRIBUTING.md5 Please read the following before filing an issue or sending a pull request.
18 [port](http://github.com/google/libphonenumber#third-party-ports),
20 * If you are using the library through a front-end or wrapper, issues
24 group](https://groups.google.com/group/libphonenumber-discuss)? If so, you
30 For acceptable evidence, [see below](#provide-supporting-evidence).
35 * Number type ("fixed-line", "mobile", "short code", etc.):
54 Ideally, change requests for ranges should be accompanied by authoritative
73 * [Corporate CLA](http://developers.google.com/open-source/cla/corporate?csw=1):
84 * [Individual CLA](http://cla.developers.google.com/about/google-individual?csw=1):
97 ## Pull requests
[all …]
Dmaking-metadata-changes.md8 Note that we cannot accept pull requests to modify metadata directly, but you may
10 upstream. Please [file a corresponding issue](CONTRIBUTING.md#checklist-before-filing-an-issue)
13 You can read more about the pull request [contribution guidelines](CONTRIBUTING.md#pull-requests).
23 * `resources/ShortNumberMetadata.xml` for short-code data
45 ant -f java/build.xml junit
56 ant -f java/build.xml build-js-metadata
77 ant -f java/build.xml jar
80 Then [run your own demo](run-java-demo.md) and test your changes are as
/third_party/jerryscript/
DCONTRIBUTING.md6 When development is complete, a patch set should be submitted via GitHub pull requests. A review of…
8 …pull request. Patches sent privately to Maintainers and Committers will not be considered. Because…
25 * http://www.apache.org/licenses/LICENSE-2.0
35 …-wide notice ("Copyright JS Foundation and other contributors, http://js.foundation") is not permi…
39 …-off is a simple line at the end of the commit message of the patch, which certifies that you wrot…
41 We have the same requirements for using the signed-off-by process as the Linux kernel.
42 In short, you need to include a signed-off-by tag in every patch.
46 > JerryScript-DCO-1.0-Signed-off-by: Random J Developer random@developer.example.org
48 "JerryScript-DCO-1.0-Signed-off-by:" this is a developer's certification that he or she has the rig…
50 ### 4. Open a GitHub [pull request](https://github.com/jerryscript-project/jerryscript/pulls)
[all …]
/third_party/vk-gl-cts/external/vulkan-docs/src/
DREADMESC.adoc1 // Copyright 2017-2024 The Khronos Group Inc.
2 // SPDX-License-Identifier: CC-BY-4.0
4 ifdef::env-github[]
5 :note-caption: :information_source:
10 The link:https://github.com/KhronosGroup/VulkanSC-Docs[VulkanSC-Docs]
20 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers] under the `sc_main` branch)
22 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers] under the `sc_main` branch)
26 link:https://github.com/KhronosGroup/VulkanSC-Docs[VulkanSC-Docs].
28 changes (Pull Requests) against the Specification, subject to approval by
32 link:https://github.com/KhronosGroup/VulkanSC-Docs/issues/[Issues]
[all …]
DREADMEVK.adoc1 // Copyright 2017-2024 The Khronos Group Inc.
2 // SPDX-License-Identifier: CC-BY-4.0
4 ifdef::env-github[]
5 :note-caption: :information_source:
10 The link:https://github.com/KhronosGroup/Vulkan-Docs[Vulkan-Docs]
20 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers])
22 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers])
26 link:https://github.com/KhronosGroup/Vulkan-Docs/[Vulkan-Docs].
28 changes (Pull Requests) against the Specification, subject to approval by
32 …ulkan-Web-Registry/blob/main/Vulkan-Projects.adoc[Vulkan-Projects] list on the link:https://github…
[all …]
/third_party/rust/crates/rust-cexpr/
D.travis.yml3 # This is where pull requests from "bors r+" are built.
4 - staging
5 # This is where pull requests from "bors try" are built.
6 - trying
8 - master
14 - libclang-dev
16 - RUST_BACKTRACE=1 LLVM_CONFIG_PATH=llvm-3.8-config
18 - cargo test --verbose --all
/third_party/cJSON/.github/
DCONTRIBUTING.md4 …e welcome. If you find a bug or want to improve cJSON in another way, pull requests are appreciate…
6 …asted effort, please open an issue to discuss the technical details before creating a pull request.
11 --------
12 …ke pull requests to the `master` branch for small bug- or security fixes (these are usually just a…
15 ------------
35 if ((buffer == NULL) || (buffer->buffer == NULL))
39 buffer_pointer = buffer->buffer + buffer->offset;
41 buffer->offset += strlen((const char*)buffer_pointer);
46 ----------
52 -----------
/third_party/grpc/src/python/
DCONTRIBUTING.md8 …lows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
12 …lows [gRPC Guidelines for Pull Requests](https://github.com/grpc/grpc/blob/master/CONTRIBUTING.md#…
28 …your system. If not, download and install it from the [official Git website](https://git-scm.com/).
29 * **GitHub Account:** You'll need a GitHub account to fork the repository and submit pull requests.
37 …ps://github.com/grpc/grpc/issues?q=is%3Aissue+is%3Aopen+label%3Alang%2Fpython+sort%3Aupdated-desc).
38 …n on an issue, feel free to ask questions on the [gRPC forum](https://groups.google.com/g/grpc-io).
42 ```git clone https://github.com/<your-username>/grpc.git```
46 git submodule update --init --recursive
49 ```git checkout -b my-feature-branch```
51 * Create a new virtual environment by running:```python -m venv ~/.virtualenvs/grpc-python```
[all …]
/third_party/libbpf/
D.travis.yml5 - docker
9 - PROJECT_NAME='libbpf'
10 - AUTHOR_EMAIL="$(git log -1 --pretty=\"%aE\")"
11 - REPO_ROOT="$TRAVIS_BUILD_DIR"
12 - CI_ROOT="$REPO_ROOT/travis-ci"
13 - VMTEST_ROOT="$CI_ROOT/vmtest"
18 - qemu-kvm
19 - zstd
20 - binutils-dev
21 - elfutils
[all …]
/third_party/spirv-tools/
DCONTRIBUTING.md1 # Contributing to SPIR-V Tools
6 [Tracking SPIRV-Tools work with GitHub projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/m…
11 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
12 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
14 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
20 issue is about. Simply using "Segfault in spirv-opt" is not helpful
29 For feature requests, we use
30 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
39 [Khronos Open Source Contributor License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Too…
43 need to be sure of various other things -- for instance that you'll tell us if
[all …]
/third_party/grpc/summerofcode/2016/
Dsiddharth_shukla.md14 - [CPython](https://www.python.org/): The reference implementation
15 - [Jython](http://www.jython.org/): Python implemented in Java
16 - [Python for .NET](http://pythonnet.sourceforge.net/): CPython implementation that enables .NET li…
17 - [IronPython](http://ironpython.net/): Python implemented in .NET
18 - [PyPy](http://pypy.org/): Python implemented completely in Python
19 - [Stackless](https://bitbucket.org/stackless-dev/stackless/wiki/Home): Replaces the dependency for…
27 support because PyPy has a non-deterministic garbage collector that does
38 - [Enable py35 and py36 testing](https://github.com/grpc/grpc/commit/c478214e475e103c5cdf477f0adc18…
39 - [Make testing toolchain python 3.x compliant](https://github.com/grpc/grpc/commit/0589e533cd65a2c…
40 - [Add .idea folder to .gitignore](https://github.com/grpc/grpc/commit/365ef40947e22b5438a63f123679…
[all …]
/third_party/skia/third_party/externals/spirv-tools/
DCONTRIBUTING.md1 # Contributing to SPIR-V Tools
5 We organize known future work in GitHub projects. See [Tracking SPIRV-Tools work
7 projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/master/docs/projects.md)
12 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
13 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
15 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
21 issue is about. Simply using "Segfault in spirv-opt" is not helpful
30 For feature requests, we use
31 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
40 License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Tools) (CLA),
[all …]
/third_party/skia/third_party/externals/swiftshader/third_party/SPIRV-Tools/
DCONTRIBUTING.md1 # Contributing to SPIR-V Tools
5 We organize known future work in GitHub projects. See [Tracking SPIRV-Tools work
7 projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/master/docs/projects.md)
12 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
13 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
15 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
21 issue is about. Simply using "Segfault in spirv-opt" is not helpful
30 For feature requests, we use
31 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
40 License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Tools) (CLA),
[all …]
/third_party/rust/crates/serde/
DCONTRIBUTING.md4 reports, pull requests, and feedback. This document gives some guidance if you
7 ## Submitting bug reports and feature requests
9 Serde development is spread across lots of repositories, but this serde-rs/serde
26 pull request with your changes. If anything does not pass, typically it will be
34 cargo test --features derive
41 cargo +nightly test --features unstable
46 [`serde`]: https://github.com/serde-rs/serde/tree/master/serde
47 [`test_suite`]: https://github.com/serde-rs/serde/tree/master/test_suite
51 In all Serde-related forums, we follow the [Rust Code of Conduct]. For
55 [Rust Code of Conduct]: https://www.rust-lang.org/policies/code-of-conduct

12345678910>>...13