Searched +full:- +full:- +full:onto +full:- +full:branch (Results 1 – 25 of 473) sorted by relevance
12345678910>>...19
| /external/pytorch/.github/scripts/ |
| D | tryrebase.py | 16 …"\n```\nAborting rebase because rebasing the branch resulted in the same sha as the target branch.…
21 def parse_args() -> Any:
24 parser = ArgumentParser("Rebase PR into branch")
25 parser.add_argument("--dry-run", action="store_true")
26 parser.add_argument("--branch", type=str)
33 ) -> None:
42 msg += f"\n`@pytorchbot rebase -b {def_branch}`"
55 ) -> bool:
56 branch = f"pull/{pr.pr_num}/head"
58 refspec = f"{branch}:{pr.head_ref()}"
[all …]
|
| D | cherry_pick.py | 23 def parse_args() -> Any:
26 parser = ArgumentParser("cherry pick a landed PR onto a release branch")
28 "--onto-branch", type=str, required=True, help="the target release branch"
31 "--github-actor", type=str, required=True, help="all the world's a stage"
34 "--classification",
41 "--fixes",
46 parser.add_argument("--dry-run", action="store_true")
51 def get_merge_commit_sha(repo: GitRepo, pr: GitHubPR) -> Optional[str]:
60 def get_release_version(onto_branch: str) -> Optional[str]:
62 Return the release version if the target branch is a release branch
[all …]
|
| D | test_tryrebase.py | 10 def mocked_rev_parse(branch: str) -> str:
11 return branch
29 ) -> None:
39 "-f",
46 f"Successfully rebased `master` onto `{MAIN_BRANCH}`",
60 ) -> None:
70 "-f",
77 f"Successfully rebased `master` onto `{VIABLE_STRICT_BRANCH}`",
82 @mock.patch("gitutils.GitRepo._run_git", return_value="Everything up-to-date")
91 ) -> None:
[all …]
|
| /external/executorch/.github/scripts/ |
| D | cherry_pick.py | 5 # This source code is licensed under the BSD-style license found in the
30 def parse_args() -> Any:
33 parser = ArgumentParser("cherry pick a landed PR onto a release branch")
35 "--onto-branch", type=str, required=True, help="the target release branch"
38 "--github-actor", type=str, required=True, help="all the world's a stage"
41 "--classification",
48 "--fixes",
53 parser.add_argument("--dry-run", action="store_true")
58 def get_merge_commit_sha(repo: GitRepo, pr: GitHubPR) -> Optional[str]:
67 def get_release_version(onto_branch: str) -> Optional[str]:
[all …]
|
| /external/pytorch/ |
| D | RELEASE.md | 3 <!-- toc -->
5 - [Release Compatibility Matrix](#release-compatibility-matrix)
6 - [Release Cadence](#release-cadence)
7 - [General Overview](#general-overview)
8 - [Frequently Asked Questions](#frequently-asked-questions)
9 - [Cutting a release branch preparations](#cutting-a-release-branch-preparations)
10 - [Cutting release branches](#cutting-release-branches)
11 - [`pytorch/pytorch`](#pytorchpytorch)
12 - [`pytorch/builder` / PyTorch domain libraries](#pytorchbuilder--pytorch-domain-libraries)
13 …- [Making release branch specific changes for PyTorch](#making-release-branch-specific-changes-for…
[all …]
|
| /external/openscreen/docs/ |
| D | advanced_gerrit.md | 16 [Change-Id commit-msg hook](https://gerrit-documentation.storage.googleapis.com/Documentation/2.14.…
17 This adds a `Change-Id` line to each commit message locally, which Gerrit uses
21 To download the commit-msg hook for the Open Screen repository, use the
25 curl -Lo .git/hooks/commit-msg https://chromium-review.googlesource.com/tools/hooks/commit-msg
26 chmod a+x .git/hooks/commit-msg
31 You should run `git cl presubmit --upload` in the root of the repository before pushing for
39 current branch. If you upload again, it uploads on the same issue (which is tied
40 to the branch, not the commit). See the [git-cl](https://chromium.googlesource.com/chromium/tools/d…
47 of the commit you are pushing has a Change-Id line, that change will also be the
52 Change-Id: aaa and this is in the process of being reviewed on Gerrit. Now
[all …]
|
| /external/sdv/vsomeip/third_party/boost/phoenix/doc/ |
| D | maintenance.qbk | 56 * It is up to the maintainer to put patches and tests onto develop and see whether there are any re…
69 * I have been making most of the changes on branch develop or on branches from it.
70 * I test the changes on the develop branch.
71 * When I want to move things from develop to master I first branch from develop a new branch which …
73 * I now also have a separate branch for developing and testing documentation changes.
74 * I move selected changes from documentation onto the develop branch and then onto master branch.
107 * __clang__ 3.4, 3.5 & 3.6 (pre-release in the last case)
|
| /external/nullaway/.github/workflows/ |
| D | run_gcp_benchmarks.sh | 3 # This script is responsible for running benchmarks for a GitHub pull request and the main branch o…
9 # Using gcloud compute scp to copy the bash scripts that will run the benchmarks onto the GCCE
10 … scp ./.github/workflows/run_pr_benchmarks.sh root@nullway-jmh:"$BRANCH_NAME/" --zone=us-central1-a
11 …cp ./.github/workflows/run_main_benchmarks.sh root@nullway-jmh:"$BRANCH_NAME/" --zone=us-central1-a
13 # Running the benchmark script for the pull request branch and main branch on GCCE
16 # Copying the benchmark results from GCCE back to the Github runner for the PR branch
17 …ud compute scp root@nullway-jmh:"$BRANCH_NAME/pr/NullAway/jmh/build/results/jmh/results.txt" ./pr_…
19 # Copying the benchmark results from GCCE back to the Github runner for the main branch
20 … compute scp root@nullway-jmh:"$BRANCH_NAME/main/NullAway/jmh/build/results/jmh/results.txt" ./mai…
|
| /external/perfetto/docs/visualization/ |
| D | perfetto-ui-release-process.md | 6 - `stable`, the version served by default on ui.perfetto.dev.
8 - `canary`, a less stable but fresher release. Updated every 1-2 weeks.
9 - `autopush`, the current HEAD version of the UI. Unstable.
13 - Week 1: Update `canary` to `HEAD`.
14 - Week 2: Update `canary` to `HEAD`.
16 Only critical bug fixes can be cherry-picked onto `canary`.
17 - Week 3: Canary stabilization week 2/2.
18 - Week 4: Update `stable` to current `canary`, update `canary` to `HEAD`.
23 - Canary soaks for two weeks before being promoted to stable.
24 - Newer features can be tried out in Canary within a week, or two at most (if
[all …]
|
| /external/executorch/build/ |
| D | pick_doc_commits.py | 5 # This source code is licensed under the BSD-style license found in the
8 """Helps find commits to cherrypick into a release branch.
11 pick_doc_commits.py --main=origin/main --release=origin/release/5.5
13 It will find commits on the main branch that are not on the release branch, and
14 filter them down to the docs-only commits that should be cherrypicked. It will
21 care which branch is currently checked out.
34 # Controlled by the --verbose flag.
45 def run_git(command: List[str]) -> List[str]:
54 A list of the non-empty lines printed to stdout, without trailing
66 # Remove empty and whitespace-only lines.
[all …]
|
| /external/pytorch/.github/workflows/ |
| D | cherry-pick.yml | 5 types: [try-cherry-pick]
8 cherry-pick:
9 name: cherry-pick-pr-${{ github.event.client_payload.pr_num }}
10 runs-on: ubuntu-latest
11 environment: cherry-pick-bot
15 - name: Checkout repo
19 fetch-depth: 0
22 - name: Setup Python
23 uses: actions/setup-python@v4
25 python-version: '3.11'
[all …]
|
| /external/executorch/.github/workflows/ |
| D | cherry-pick.yml | 5 types: [try-cherry-pick]
8 cherry-pick:
9 name: cherry-pick-pr-${{ github.event.client_payload.pr_num }}
10 runs-on: ubuntu-latest
11 environment: cherry-pick-bot
15 - name: Checkout repo
19 fetch-depth: 0
23 - name: Setup Python
24 uses: actions/setup-python@v4
26 python-version: '3.10'
[all …]
|
| /external/kotlinx.coroutines/ |
| D | RELEASE.md | 3 To release a new `<version>` of `kotlinx-coroutines`:
5 1. Checkout the `develop` branch: <br>
11 3. Make sure the `master` branch is fully merged into `develop`:
14 4. Search & replace `<old-version>` with `<version>` across the project files. Should replace in:
17 * [`kotlinx-coroutines-debug/README.md`](kotlinx-coroutines-debug/README.md)
18 * [`kotlinx-coroutines-test/README.md`](kotlinx-coroutines-test/README.md)
19 * [`coroutines-guide-ui.md`](ui/coroutines-guide-ui.md)
22 * [`integration-testing/gradle.properties`](integration-testing/gradle.properties)
25 As an alternative approach, you can use `./bump-version.sh new_version`
32 6. Create the branch for this release:
[all …]
|
| /external/apache-commons-bcel/src/site/xdoc/manual/ |
| D | jvm.xml | 2 <!--
11 * http://www.apache.org/licenses/LICENSE-2.0
19 -->
30 with <a href="bcel-api.html">section 3</a>.
66 href="http://www.robert-tolksdorf.de/vmlanguages.html">other
83 check at run-time, i.e. the byte code verifier.
97 additional, user-defined information into class file data
100 specification declares that unknown, i.e., user-defined attributes
113 symbolic references to classes, fields and methods at run-time is
126 well-known statement:
[all …]
|
| /external/arm-trusted-firmware/docs/process/ |
| D | faq.rst | 1 Frequently-Asked Questions (FAQ)
5 ---------------------------
14 ------------------------------------------------------------
33 bug-fixes but may wait up to a week to merge major changes, or ones requiring
45 ------------------------------------------------------------------------------
51 Typically, it will be 1-2 days.
55 patches will be merged onto ``integration``, which will temporarily diverge from
56 the release branch. The ``integration`` branch will be rebased onto ``master``
57 after the release, and then ``master`` will be fast-forwarded to ``integration``
58 1-2 days later. This whole process could take up 4 weeks. Please refer to the
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/process/ |
| D | faq.rst | 1 Frequently-Asked Questions (FAQ)
5 ---------------------------
14 ------------------------------------------------------------
33 bug-fixes but may wait up to a week to merge major changes, or ones requiring
45 ------------------------------------------------------------------------------
51 Typically, it will be 1-2 days.
55 patches will be merged onto ``integration``, which will temporarily diverge from
56 the release branch. The ``integration`` branch will be rebased onto ``master``
57 after the release, and then ``master`` will be fast-forwarded to ``integration``
58 1-2 days later. This whole process could take up 4 weeks. Please refer to the
[all …]
|
| /external/coreboot/util/scripts/ |
| D | gerrit-rebase | 2 # SPDX-License-Identifier: GPL-2.0-only
4 # $0 from-branch to-branch
6 # applies all commits that from-branch has over to-branch,
7 # based on a common ancestor and gerrit meta-data
16 # The first pick was Change-Id, but it was lost too often,
17 # so go for Reviewed-on instead. It's also unique because it
20 match_string='[-A-Za-z]*[Rr]eviewed-on:'
24 # This allows cutting down on commits that are re-evaluated on every run.
30 # For a $match_string of ~ "Reviewed-on: " this might
35 custom_root='^Gerrit-Rebase-Ignore-CLs-Before:'
[all …]
|
| /external/executorch/examples/demo-apps/apple_ios/LLaMA/docs/delegates/ |
| D | mps_README.md | 6 2. Building and linking libraries that are required to inference on-device for iOS platform using M…
12 …he [Setting up ExecuTorch](https://pytorch.org/executorch/stable/getting-started-setup) to set up …
15 …ructions to install it [here](https://conda.io/projects/conda/en/latest/user-guide/install/index.h…
20 conda create -n et_mps python=3.10.0
30 git submodule update --init
40 In this demo app, we support text-only inference with Llama 3.1, Llama 3, and Llama 2 models.
50 …-m examples.models.llama.export_llama --checkpoint "${MODEL_DIR}/consolidated.00.pth" --params "${…
56 * Drag&drop the model and tokenizer files onto the Simulator window and save them somewhere inside …
57 * Pick the files in the app dialog, type a prompt and click the arrow-up button.
60 * Wire-connect the device and open the contents in Finder.
[all …]
|
| /external/stressapptest/src/ |
| D | findmask.c | 7 * http://www.apache.org/licenses/LICENSE-2.0
19 * controller uses to interleave addresses onto its two channels. To use it,
29 * onto all supplied addresses, counting the amount of times this results in
57 __attribute__((optimize(3, "unroll-loops")))
74 // Fold high and low 32 bits onto each other in thread_func()
78 // Fold high and low 16 bits onto each other in thread_func()
82 // Fold high and low 8 bits onto each other in thread_func()
90 // Increment either 'a' or 'b' without needing another branch in thread_func()
|
| /external/autotest/server/site_tests/provision_FactoryImage/ |
| D | control | 2 # Use of this source code is governed by a BSD-style license that can be
11 AUTHOR = "beeps@google.com, chromeos-lab-infrastructure@google.com"
19 This test installs a specified factory image onto a servo-connected DUT.
20 It will attempt to retrieve the factory image from the canary branch, and
21 as such, the image_name must correspond to the name on that branch. For
22 example, to install the daisy_spring image from the canary-channel, one
23 would specify an image_name like: "daisy-spring/4262.320.0".
27 test_that <remote_ip> provision_FactoryImage --board=<board> \
28 --args="image_name=<board>/<build> servo_host=<ip of servo_host>"
41 raise error.AutoservError('Please specify --args="image_name=<board>/'
[all …]
|
| /external/clang/include/clang/StaticAnalyzer/Core/PathSensitive/ |
| D | CoreEngine.h | 1 //==- CoreEngine.h - Path-Sensitive Dataflow Engine ----------------*- C++ -*-//
8 //===----------------------------------------------------------------------===//
10 // This file defines a generic engine for intraprocedural, path-sensitive,
13 //===----------------------------------------------------------------------===//
34 //===----------------------------------------------------------------------===//
35 /// CoreEngine - Implements the core logic of the graph-reachability
41 /// at the statement and block-level. The analyses themselves must implement
42 /// any transfer function logic and the sub-expression level (if any).
62 /// G - The simulation graph. Each node is a (location,state) pair.
65 /// WList - A set of queued nodes that need to be processed by the
[all …]
|
| /external/rust/android-crates-io/crates/zerotrie/src/builder/ |
| D | mod.rs | 3 // (online at: https://github.com/unicode-org/icu4x/blob/main/LICENSE ).
9 //! - [konst::ZeroTrieBuilderConst] allows for human-readable const construction
10 //! - [nonconst::ZeroTrieBuilder] has the full feaure set but requires `alloc`
19 //! In the simple case of [`ZeroTrieSimpleAscii`], all nodes are binary-search, so if the input
25 //! - `prefix_len` indicates the byte index we are currently processing.
26 //! - `i` and `j` bracket a window of strings in the input that share the same prefix.
27 //! - `current_len` is the length in bytes of the current self-contained trie.
28 //! - `lengths_stack` contains metadata for branch nodes.
32 //! - "" → 11
33 //! - "ad" → 22
[all …]
|
| /external/autotest/server/cros/tradefed/ |
| D | push_arc_image.py | 2 # Use of this source code is governed by a BSD-style license that can be
8 _BUILDS_BUCKET = 'gs://chromeos-arc-images/builds'
11 'armeabi-v7a': 'arm',
12 'arm64-v8a': 'arm64',
20 'pi-arc': 7740639,
21 'rvc-arc': 7741959,
22 'sc-arc-dev': 7743996,
32 This uses the push_to_device.py tool to push the image onto the host.
35 @param branch_prefix: the branch name prefix of where the image is
36 (e.g. rvc-arc, pi-arc). This does not have to be
[all …]
|
| /external/crosvm/tools/ |
| D | cl | 3 # Use of this source code is governed by a BSD-style license that can be
28 You need to be on a local branch tracking a remote one. `repo start` does this
31 $ git checkout -b mybranch --track origin/main
37 If you are tracking a different branch (e.g. aosp/main or cros/chromeos), the upload may
39 create a new branch tracking origin/main and cherry-picks your commits.
42 [mybranch-upstream] ... resolve conflicts
43 [mybranch-upstream] $ git add .
44 [mybranch-upstream] $ git cherry-pick --continue
45 [mybranch-upstream] $ ./tools/cl upload
49 GERRIT_URL = "https://chromium-review.googlesource.com"
[all …]
|
| /external/rust/android-crates-io/crates/grpcio-sys/grpc/tools/distrib/python/ |
| D | docgen.py | 8 # http://www.apache.org/licenses/LICENSE-2.0
29 parser.add_argument('--repo-owner',
32 parser.add_argument('--doc-branch',
34 default='python-doc-%s' % grpc_version.VERSION)
52 ['python3', '-m', 'virtualenv', VIRTUALENV_DIR],
56 [PYTHON_PATH, '-m', 'pip', 'install', '--upgrade', 'pip==19.3.1'],
57 [PYTHON_PATH, '-m', 'pip', 'install', '-r', REQUIREMENTS_PATH],
58 [PYTHON_PATH, '-m', 'pip', 'install', '--upgrade', 'Sphinx'],
68 print('-' * tty_width)
71 'To push to a GitHub repo, please provide repo owner and doc branch name'
[all …]
|
12345678910>>...19