Searched full:pull (Results 1 – 25 of 2002) sorted by relevance
12345678910>>...81
12 ([#2117](https://github.com/nix-rust/nix/pull/2117))18 ([#1925](https://github.com/nix-rust/nix/pull/1925))20 correctly on Linux platforms. ([#2041](https://github.com/nix-rust/nix/pull/2041))25 ([#2061](https://github.com/nix-rust/nix/pull/2061))27 ([#2095](https://github.com/nix-rust/nix/pull/2095))32 ([#1964](https://github.com/nix-rust/nix/pull/1964))37 ([#1821](https://github.com/nix-rust/nix/pull/1821))43 ([#1871](https://github.com/nix-rust/nix/pull/1871))46 ([#1877](https://github.com/nix-rust/nix/pull/1877))48 ([#1849](https://github.com/nix-rust/nix/pull/1849))[all …]
55 # Pull requests57 GitHub pull requests are the primary mechanism we use to change nix. GitHub itself has58 some [great documentation][pr-docs] on using the Pull Request feature. We use the 'fork and59 pull' model described there.61 Please make pull requests against the `master` branch.69 [pr-docs]: https://help.github.com/articles/using-pull-requests/73 nix has a test suite that you can run with `cargo test`. Ideally, we'd like pull80 will run once you open a pull request.97 All pull requests are merged via [bors], an integration bot. After the98 pull request has been reviewed, the reviewer will leave a comment like
20 [#10414](https://github.com/rust-lang/rust-clippy/pull/10414)22 [#10362](https://github.com/rust-lang/rust-clippy/pull/10362)24 [#10528](https://github.com/rust-lang/rust-clippy/pull/10528)26 [#10448](https://github.com/rust-lang/rust-clippy/pull/10448)28 [#10415](https://github.com/rust-lang/rust-clippy/pull/10415)30 [#10467](https://github.com/rust-lang/rust-clippy/pull/10467)32 [#10543](https://github.com/rust-lang/rust-clippy/pull/10543)34 [#10481](https://github.com/rust-lang/rust-clippy/pull/10481)36 [#10497](https://github.com/rust-lang/rust-clippy/pull/10497)38 [#9102](https://github.com/rust-lang/rust-clippy/pull/9102)[all …]
8 * https://github.com/yaml/pyyaml/pull/808 -- Support for Cython 3.x and Python 3.1312 * https://github.com/yaml/pyyaml/pull/702 -- pin Cython build dep to < 3.016 * https://github.com/yaml/pyyaml/pull/327 -- Change README format to Markdown17 * https://github.com/yaml/pyyaml/pull/483 -- Add a test for YAML 1.1 types18 * https://github.com/yaml/pyyaml/pull/497 -- fix float resolver to ignore `.` and `._`19 * https://github.com/yaml/pyyaml/pull/550 -- drop Python 2.720 * https://github.com/yaml/pyyaml/pull/553 -- Fix spelling of “hexadecimal”21 * https://github.com/yaml/pyyaml/pull/556 -- fix representation of Enum subclasses22 * https://github.com/yaml/pyyaml/pull/557 -- fix libyaml extension compiler warnings23 * https://github.com/yaml/pyyaml/pull/560 -- fix ResourceWarning on leaked file descriptors[all …]
5 [#252]: https://github.com/bitflags/bitflags/pull/25611 [#252]: https://github.com/bitflags/bitflags/pull/25243 [#187]: https://github.com/bitflags/bitflags/pull/18744 [#202]: https://github.com/bitflags/bitflags/pull/20245 [#206]: https://github.com/bitflags/bitflags/pull/20646 [#207]: https://github.com/bitflags/bitflags/pull/20747 [#211]: https://github.com/bitflags/bitflags/pull/21148 [#225]: https://github.com/bitflags/bitflags/pull/22549 [#227]: https://github.com/bitflags/bitflags/pull/22750 [#229]: https://github.com/bitflags/bitflags/pull/229[all …]
1468 logic: When attempting to set no pull-up or pull-down (floating),1469 it would, instead, select pull-down.3724 first time. Having a pull-up resistor on MISO may avoid this3726 without pull-up.12085 - SAM3/4: Fix GPIO pull-up/down code. Enabling the pull-down resistor12086 while the pull-up resistor is still enabled is not possible. In this12088 Likewise, enabling the pull-up resistor while the pull-down resistor14263 slave contending with the push-pull during the ACK. From David16439 - XMC4500-Relax: Setup max. freq. 120MHz and setup pull-up to UART16970 - STM32 HRTIM: Add HRTIM push-pull mode configuration. From[all …]
13 resolve, push, pull, fetch30 [own fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-f…35 1. [Clone your fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/wo…46 [guidelines](https://github.com/grpc/grpc/blob/master/CONTRIBUTING.md#guidelines-for-pull-requests).48 ### Prepare a Pull Request54 18 … Change how `#![cfg(FALSE)]` behaves on crate root](https://github.com/rust-lang/rust/pull/110141/)19 - [Stabilize inline asm for LoongArch64](https://github.com/rust-lang/rust/pull/111235/)20 - [Uplift `clippy::undropped_manually_drops` lint](https://github.com/rust-lang/rust/pull/111530/)21 - [Uplift `clippy::invalid_utf8_in_unchecked` lint](https://github.com/rust-lang/rust/pull/111543/)22 - [Uplift `clippy::cast_ref_to_mut` lint](https://github.com/rust-lang/rust/pull/111567/)23 - [Uplift `clippy::cmp_nan` lint](https://github.com/rust-lang/rust/pull/111818/)24 - [resolve: Remove artificial import ambiguity errors](https://github.com/rust-lang/rust/pull/11208…25 …pes with Self: Sized bounds in `dyn Trait` objects](https://github.com/rust-lang/rust/pull/112319/)32 … `cfg`-ed out items to mention them in diagnostics](https://github.com/rust-lang/rust/pull/109005/)[all …]
11 …rly true), `system` or `no` (formerly false) [#77703](https://github.com/rust-lang/rust/pull/77703)12 …l accepted by `./configure`, with a warning. [#82451](https://github.com/rust-lang/rust/pull/82451)13 …mmands to match the component they generate. [#90684](https://github.com/rust-lang/rust/pull/90684)18 …check mode is not affected by this change. [#105702](https://github.com/rust-lang/rust/pull/105702)19 …n bootstrap to change the minimum version. [#108619](https://github.com/rust-lang/rust/pull/108619)20 … has been renamed to `rust.omit-git-hash`. [#110059](https://github.com/rust-lang/rust/pull/110059)25 … needs opt-in to check tests (--all-targets) [#77473](https://github.com/rust-lang/rust/pull/77473)26 …t `bootstrap/defaults/config.toml.$PROFILE`) [#77558](https://github.com/rust-lang/rust/pull/77558)28 from the default rust toolchain. [#78513](https://github.com/rust-lang/rust/pull/78513)31 …path option for each target independently. [#111242](https://github.com/rust-lang/rust/pull/111242)[all …]
3 …m/hermitcore/libhermit-rs), a Rust-based unikernel [#41](https://github.com/softprops/atty/pull/41)11 …n the unix family so redox cfg is no longer needed [#35](https://github.com/softprops/atty/pull/35)15 * fix msys detection with `winapi@0.3.5` [#28](https://github.com/softprops/atty/pull/28)19 * fix wasm regression [#27](https://github.com/softprops/atty/pull/27)23 * Fix fix pty detection [#25](https://github.com/softprops/atty/pull/25)27 * Fix an inverted condition on MinGW [#22](https://github.com/softprops/atty/pull/22)31 * Change `||` to `&&` for whether MSYS is a tty [#24](https://github.com/softprops/atty/pull/24/)35 …[0.3](https://retep998.github.io/blog/winapi-0.3/) [#18](https://github.com/softprops/atty/pull/18)39 * added support for Wasm compile targets [#17](https://github.com/softprops/atty/pull/17)43 * added support for Wasm compile targets [#17](https://github.com/softprops/atty/pull/17)[all …]
5 ## git request-pull output:12 git request-pull axboe-tree/master your_fork_URL your_branch_name14 Then replace this with the output of `git request-pull` command.20 <summary>Click to show/hide pull request guidelines</summary>22 ## Pull Request Guidelines23 1. To make everyone easily filter pull request from the email24 notification, use `[GIT PULL]` as a prefix in your PR title.26 [GIT PULL] Your Pull Request Title46 Note that all of this goes in the commit message, not in the pull47 request text. The pull request text should introduce what this pull[all …]
14 … // Entire subgraph is pull (except for a single send/push handoff output). in main()18 "If entire subgraph is pull, should have only one handoff output." in main()39 … // Entire subgraph is pull (except for a single send/push handoff output). in main()43 "If entire subgraph is pull, should have only one handoff output." in main()64 … // Entire subgraph is pull (except for a single send/push handoff output). in main()68 "If entire subgraph is pull, should have only one handoff output." in main()89 … // Entire subgraph is pull (except for a single send/push handoff output). in main()93 "If entire subgraph is pull, should have only one handoff output." in main()114 … // Entire subgraph is pull (except for a single send/push handoff output). in main()118 "If entire subgraph is pull, should have only one handoff output." in main()[all …]
13 … // Entire subgraph is pull (except for a single send/push handoff output). in main()17 "If entire subgraph is pull, should have only one handoff output." in main()38 … // Entire subgraph is pull (except for a single send/push handoff output). in main()42 "If entire subgraph is pull, should have only one handoff output." in main()62 … // Entire subgraph is pull (except for a single send/push handoff output). in main()66 "If entire subgraph is pull, should have only one handoff output." in main()82 // Entire subgraph is pull (except for a single send/push handoff output). in main()86 "If entire subgraph is pull, should have only one handoff output." in main()102 … // Entire subgraph is pull (except for a single send/push handoff output). in main()106 "If entire subgraph is pull, should have only one handoff output." in main()[all …]
31 * Fix potential core dumped for strrchr, see [#546](https://github.com/DaveGamble/cJSON/pull/546)32 …null pointer crash in cJSON_CreateXxArray, see [#538](https://github.com/DaveGamble/cJSON/pull/538)33 …ll pointer problems on allocation failure, see [#526](https://github.com/DaveGamble/cJSON/pull/526)34 * Fix a possible dereference of null pointer, see [#519](https://github.com/DaveGamble/cJSON/pull/5…35 * Fix windows build failure about defining nan, see [#518](https://github.com/DaveGamble/cJSON/pull…41 * optimize the way to find tail node, see [#503](https://github.com/DaveGamble/cJSON/pull/503)42 …osx because NAN is a float. Thanks @sappo, see [#484](https://github.com/DaveGamble/cJSON/pull/484)43 … in detach and replace. Thanks @miaoerduo, see [#456](https://github.com/DaveGamble/cJSON/pull/456)49 …t breaking changes. Thanks @caglarivriz, see [#358](https://github.com/DaveGamble/cJSON/pull/358) 50 … cJSON_GetNumberValue. Thanks @Intuition, see[#385](https://github.com/DaveGamble/cJSON/pull/385) [all …]
444 1453 git pull481 1490 git pull484 1493 git pull486 1495 git pull488 1497 git pull490 1499 git pull492 1501 git pull494 1503 git pull526 1535 git pull542 1551 git pull[all …]
31 We accept patches in the form of github pull requests. If you are new to32 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…50 Before sending out your pull request, please familiarize yourself with the56 Most pull requests should go to the main branch and the change will be59 already merged to main, and then create a pull request cherry-picking the62 For each pull request, a protobuf team member will be assigned to review the63 pull request. For minor cleanups, the pull request may be merged right away69 hear from you for 2 weeks or longer, we may close the pull request. You can70 still send the pull request again once you have time to work on it.72 Once a pull request is merged, we will take care of the rest and get it into[all …]
17 …alidate version number; cleanup [\#3698](https://github.com/nlohmann/json/pull/3698) ([falbrechtsk…18 …file and update file for 3.11.2 [\#3697](https://github.com/nlohmann/json/pull/3697) ([falbrechtsk…19 - fix typo in json\_pointer.md [\#3692](https://github.com/nlohmann/json/pull/3692) ([eltociear](ht…20 - Add amalgamated json-fwd.hpp to release [\#3687](https://github.com/nlohmann/json/pull/3687) ([nl…21 - Documentation updates for 3.11.2 [\#3686](https://github.com/nlohmann/json/pull/3686) ([falbrecht…22 - Make json\_pointer usable as map key \(again\) [\#3685](https://github.com/nlohmann/json/pull/368…23 - Deprecate json\_pointer/string\_t comparisons [\#3684](https://github.com/nlohmann/json/pull/3684…24 …ersion component to be disabled [\#3683](https://github.com/nlohmann/json/pull/3683) ([falbrechtsk…25 …-string json\_pointer overloads [\#3681](https://github.com/nlohmann/json/pull/3681) ([falbrechtsk…26 - Amalgamate the forward declaration header [\#3679](https://github.com/nlohmann/json/pull/3679) ([…[all …]
6 string: ["token", "pull", "reviewer", "owner", "repo"],8 pr: "pull",14 pull: process.env.GH_PULL_NUMBER,25 if (!options.token || !options.pull || !options.reviewer || !options.owner || !options.repo) {30 const pull_number = +options.pull;52 console.log(`Failed to add ${reviewers.join(", ")} to the pull request.`);66 --repo <repo> The GH repo for the pull request (default: 'TypeScript').67 --pull <pr_number> The pull request number. Uses %GH_PULL_NUMBER% if present.
8 * [PERF #930](https://github.com/rust-lang/regex/pull/930):33 * [FEATURE #832](https://github.com/rust-lang/regex/pull/832):35 * [FEATURE #857](https://github.com/rust-lang/regex/pull/857):37 * [FEATURE #861](https://github.com/rust-lang/regex/pull/861):81 * [BUG #772](https://github.com/rust-lang/regex/pull/772):102 [PR #768](https://github.com/rust-lang/regex/pull/768) fixes the bug, which was148 * [BUG #750](https://github.com/rust-lang/regex/pull/750):160 * [BUG #362](https://github.com/rust-lang/regex/pull/362):162 * [BUG #576](https://github.com/rust-lang/regex/pull/576):164 * [BUG #728](https://github.com/rust-lang/regex/pull/749):[all …]
6 When development is complete, a patch set should be submitted via GitHub pull requests. A review of…8 Please submit all patches in public by opening a pull request. Patches sent privately to Maintainer…50 ### 4. Open a GitHub [pull request](https://github.com/jerryscript-project/jerryscript/pulls)52 You can find instructions about opening a pull request [here](https://help.github.com/articles/crea…69 Changes are submitted via pull requests and only the Maintainers and Committers should approve or r…72 ## Tips on GitHub Pull Requests77 * Pull in upstream changes often to stay up-to-date so that when you submit your pull request, merg…
37 GitHub under Issues and Pull Requests.38 * Use the existing GitHub forking and pull request process.42 [submitting a pull request](https://help.github.com/articles/using-pull-requests/).50 * The resulting Pull Request will be assigned to a repository maintainer.51 It is the maintainer's responsibility to ensure the Pull Request53 Once the Pull Request has been approved and is passing internal CI,107 error for each commit in your pull request.108 Note that to be accepted into the repository, the pull request must145 submitting your pull request or other contribution to GitHub.
12 pull = False variable15 pull = True variable17 if pull or 'pull' in sys.argv:18 subprocess.run ([git, 'pull'], cwd='aots', check=True)
37 git pull origin118 If you try to do a pull by just saying\ ``git pull`` and Git126 Otherwise, you have to say\ ``git pull origin main`` each time you127 do a pull.142 git pull157 did your last pull. Even if your changes do not conflict with their159 the point in time where you did your last pull and merging it to a166 git pull --rebase
57 * Create a pull request (PR) with your patch.92 pull request which will trigger running all CI jobs.132 * Make sure that the `upstream` remote is set to fetch from the `refs/pull`138 +refs/pull/*/head:refs/remotes/upstream/pr/*141 * If the line `+refs/pull/*/head:refs/remotes/upstream/pr/*` is not present in145 git config --local --add remote.upstream.fetch '+refs/pull/*/head:refs/remotes/upstream/pr/*'156 git pull159 * Fetch all pull requests refs:165 * Checkout the particular pull request you are going to review:184 just pushed. See https://github.com/KhronosGroup/SPIRV-Tools/pull/935 as an