Home
last modified time | relevance | path

Searched +full:cherry +full:- +full:pick (Results 1 – 25 of 162) sorted by relevance

1234567

/external/executorch/.github/scripts/
Dcherry_pick.py5 # 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",
44 help="the cherry pick category",
48 "--fixes",
51 help="the GitHub issue that the cherry pick fixes",
53 parser.add_argument("--dry-run", action="store_true")
[all …]
/external/pytorch/.github/scripts/
Dcherry_pick.py23 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",
37 help="the cherry pick category",
41 "--fixes",
44 help="the GitHub issue that the cherry pick fixes",
46 parser.add_argument("--dry-run", action="store_true")
51 def get_merge_commit_sha(repo: GitRepo, pr: GitHubPR) -> Optional[str]:
[all …]
/external/pytorch/.github/workflows/
Dcherry-pick.yml1 name: Create a cherry pick from a PR
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
[all …]
/external/executorch/.github/workflows/
Dcherry-pick.yml1 name: Create a cherry pick from a PR
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
[all …]
/external/pytorch/
DRELEASE.md3 <!-- 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/ksp/.github/workflows/
Dauto-merge.yml1 # Workflow to cherry-pick changes from main to release branch.
3 name: auto-merge
10 build-and-test:
12 fail-fast: false
14 os: [ ubuntu-latest, macos-latest ]
17 runs-on: ${{ matrix.os }}
21 - uses: actions/checkout@v2
23 fetch-depth: 0
24 ref: 1.0.10-release
26 - name: merge commits from main to release branch
[all …]
/external/crosvm/docs/book/src/integration/
Dchromeos.md13 [gerrit](https://chromium-review.googlesource.com/q/hashtag:crosvm-merge).
18 Googlers can find more information on the merge process at [go/crosvm-uprev-playbook].
23 `cros_workon` package. The full package name is `chromeos-base/crosvm`.
26 …Changes](https://www.chromium.org/chromium-os/developer-library/guides/development/developer-guide…
28 build with cros build-packages. Consecutive builds without changes to dependency can be done with
32 (chroot)$ cros_workon --board=${BOARD} start chromeos-base/crosvm
33 (chroot or host)$ cros build-packages --board=${BOARD} chromeos-base/crosvm
34 (chroot)$ emerge-${BOARD} chromeos-base/crosvm -j 10
46 (chroot)$ FEATURES=test emerge-${BOARD} chromeos-base/crosvm -j 10
60 (chroot or host)$ cros build-packages --board=${BOARD} chromeos-base/crosvm
[all …]
/external/executorch/build/
Dpick_doc_commits.py5 # This source code is licensed under the BSD-style license found in the
11 pick_doc_commits.py --main=origin/main --release=origin/release/5.5
14 filter them down to the docs-only commits that should be cherrypicked. It will
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.
70 debug_log("-----BEGIN GIT OUTPUT-----")
73 debug_log("-----END GIT OUTPUT-----")
80 """A git commit hash and its one-line message."""
[all …]
/external/perfetto/docs/contributing/
Dchrome-branches.md4 creation of a branch in the perfetto repo, cherry-picking of the change(s) to
16 [cherry-picking](#all-tables). To check, you can search for it in
17 …[Gerrit's branch page](https://android-review.googlesource.com/admin/repos/platform/external/perfe…
23 `https://chromium.googlesource.com/chromium/src.git/+/refs/branch-heads/XXXX/DEPS`
26 [`DEPS`](https://chromium.googlesource.com/chromium/src.git/+/refs/branch-heads/4280/DEPS)
29 1. Create the branch - the easiest way to do this is via
30 …[Gerrit's branch page](https://android-review.googlesource.com/admin/repos/platform/external/perfe…
31 The `NEW BRANCH` button on the top right opens a wizard - fill in the branch
34 [perfetto-dev](https://groups.google.com/forum/#!forum/perfetto-dev) mailing
37 ## Cherry-picking the change(s) {#cherry-pick}
[all …]
/external/bpftool/scripts/
Dsync-kernel.sh4 echo "USAGE: ./sync-kernel.sh <bpftool-repo> <kernel-repo>"
8 …echo " - Update the libbpf submodule, commit, and use its new checkpoints as target commits for b…
9 echo " - Cherry-pick commits from the bpf-next branch, up to the bpf-next target commit."
10 echo " - Cherry-pick commits from the bpf branch, up to the bpf target commit."
11 echo " - Create a new commit with the updated version and checkpoints."
12 echo " - Check consistency."
14 …echo "Set BPF_NEXT_BASELINE to override bpf-next tree commit, otherwise read from <bpftool-repo>/C…
15 …PF_BASELINE to override bpf tree commit, otherwise read from <bpftool-repo>/BPF-CHECKPOINT-COMMIT."
16 …t BPF_NEXT_TIP_COMMIT to override bpf-next tree target commit, otherwise read from <bpftool-repo>/…
17 … override bpf tree target commit, otherwise read from <bpftool-repo>/libbpf/BPF-CHECKPOINT-COMMIT,…
[all …]
/external/mesa3d/docs/relnotes/
D18.2.6.rst16 ----------------
20 e0ea1236dbc6c412b02e1b5d7f838072525971a6630246fa82ae4466a6d8a587 mesa-18.2.6.tar.gz
21 9ebafa4f8249df0c718e93b9ca155e3593a1239af303aa2a8b0f2056a7efdc12 mesa-18.2.6.tar.xz
24 ------------
29 ---------
31 - `Bug 107626 <https://bugs.freedesktop.org/show_bug.cgi?id=107626>`__
32 - [SNB] The graphical corruption and GPU hang occur sometimes on the
33 piglit test "arb_texture_multisample-large-float-texture" with
34 parameter --fp16
35 - `Bug 107856 <https://bugs.freedesktop.org/show_bug.cgi?id=107856>`__
[all …]
D18.2.8.rst16 ----------------
20 77512edc0a84e19c7131a0e2e5ebf1beaf1494dc4b71508fcc92d06d65f9f4f5 mesa-18.2.8.tar.gz
21 1d2ed9fd435d86d95b7215b287258d3e6b1180293a36f688e5a2efc18298d863 mesa-18.2.8.tar.xz
24 ------------
29 ---------
31 - `Bug 108114 <https://bugs.freedesktop.org/show_bug.cgi?id=108114>`__
32 - [vulkancts] new VK_KHR_16bit_storage tests fail.
33 - `Bug 108116 <https://bugs.freedesktop.org/show_bug.cgi?id=108116>`__
34 - [vulkancts] stencil partial clear tests fail.
35 - `Bug 108910 <https://bugs.freedesktop.org/show_bug.cgi?id=108910>`__
[all …]
/external/bazelbuild-rules_python/
DDEVELOPING.md25 also test-drive the commit in an existing Bazel workspace to sanity check functionality.
30 1. [Determine the next semantic version number](#determining-semantic-version)
31 1. Create a tag and push, e.g. `git tag 0.5.0 upstream/main && git push upstream --tags`
39 **rules_python** is currently using [Zero-based versioning](https://0ver.org/) and thus backwards-i…
40 changes still come under the minor-version digit. So releases with API changes and new features bum…
47 ### Patch release with cherry picks
51 release tag and the patch changes cherry-picked into it.
56 1. `git checkout -b release/0.37 0.37.0`
58 1. `git cherry-pick -x deadbeef`
60 1. `git cherry-pick --continue` (if applicable)
[all …]
/external/chromiumos-config/
Dmigration_announcement_template.md2 g/chromeos-<program>, g/chromeos-peng-sies, platform project leads, and
3 g/cros-boxster-announce.**
5 **Configuration for <program> will now be managed on a per-project basis
10 Starlark -- a Python-like configuration-management language -- will be used to
25 and backwards-compatible JSON payloads.
26 * <private overlay>: <chromeos-config-bsp ebuild> sets `CROS_WORKON_PROJECT`
56 …l](https://chromium.git.corp.google.com/chromiumos/platform2/+/HEAD/chromeos-config/cros_config_ho…
57 From the platform point-of-view, the configuration will not change.
66 4. **How will I cherry pick changes to branches?**
68 If your project has not yet created branches, you will only need to cherry pick
[all …]
/external/angle/doc/
DChoosingANGLEBranch.md26 branches will be short-lived.
48 ## Cherry-picking a change to a release branch
56 entirely in the Gerrit UI. Click the "Cherry pick" button and enter
62 2. `git cherry-pick [commit_hash]`
66 Have the cherry-pick reviewed, and then land it. It's also OK to skip
70 There is one final step to pick up the ANGLE change into a Chromium Beta or
71 Stable branch. A Skia auto-roller updates the DEPS file in the corresponding
74 these auto-rollers:
76 1. https://autoroll.skia.org/r/angle-chromium-beta-autoroll
77 1. https://autoroll.skia.org/r/angle-chromium-stable-autoroll
DCodeReviewProcess.md14 your dashboard at https://chromium-review.googlesource.com/
17 * You may view the diffs either side-to-side, or in unified diff format.
18 * You can comment on a specific line of code by double-clicking that line,
22 that pre-exist the CL are not required to be addressed in the CL. As a
23 reviewer, you can request a follow-up CL to address the style issue if
29 review (Code-Review +1 or +2).
31 comments and a neutral review. (Code-Review 0)
33 review. (Code-Review -1 or -2)
36 * ANGLE has a 2-reviewer policy for CLs. This means all changes should get
51 * Please note: Verification and commit-queue workflow may be subject to
[all …]
/external/cronet/tot/components/cronet/gn2bp/
Dgen_desc_json.sh9 # http://www.apache.org/licenses/LICENSE-2.0
21 # -d dir: The directory that points to a local checkout of chromium/src.
22 # -r rev: The reference revision of upstream Chromium to use. Must match the
25 # -f: Force reset the chromium/src directory.
27 set -e -x
33 Usage: gen_gn_desc.sh -d dir -r rev [-f]
51 local -r rev="$1"
52 local -r chromium_dir="$2"
53 local -r force_reset="$3"
56 git fetch --tags
[all …]
/external/cronet/stable/components/cronet/gn2bp/
Dgen_desc_json.sh9 # http://www.apache.org/licenses/LICENSE-2.0
21 # -d dir: The directory that points to a local checkout of chromium/src.
22 # -r rev: The reference revision of upstream Chromium to use. Must match the
25 # -f: Force reset the chromium/src directory.
27 set -e -x
33 Usage: gen_gn_desc.sh -d dir -r rev [-f]
51 local -r rev="$1"
52 local -r chromium_dir="$2"
53 local -r force_reset="$3"
56 git fetch --tags
[all …]
/external/libbpf/scripts/
Dsync-kernel.sh4 echo "USAGE: ./sync-kernel.sh <libbpf-repo> <kernel-repo> <bpf-branch>"
6 …echo "Set BPF_NEXT_BASELINE to override bpf-next tree commit, otherwise read from <libbpf-repo>/CH…
7 …BPF_BASELINE to override bpf tree commit, otherwise read from <libbpf-repo>/BPF-CHECKPOINT-COMMIT."
8 echo "Set MANUAL_MODE to 1 to manually control every cherry-picked commits."
12 set -eu
14 LIBBPF_REPO=${1-""}
15 LINUX_REPO=${2-""}
16 BPF_BRANCH=${3-""}
17 BASELINE_COMMIT=${BPF_NEXT_BASELINE:-$(cat ${LIBBPF_REPO}/CHECKPOINT-COMMIT)}
18 BPF_BASELINE_COMMIT=${BPF_BASELINE:-$(cat ${LIBBPF_REPO}/BPF-CHECKPOINT-COMMIT)}
[all …]
/external/coreboot/util/scripts/
Dcross-repo-cherrypick2 # cross-repo-cherrypick - rebase helper script
4 # SPDX-License-Identifier: GPL-2.0-only
10 # do the following at the end of a larger cherry-pick series:
12 # git checkout -b upstreaming
13 # git cherry-pick ...
14 # git rebase -i --exec util/scripts/cross-repo-cherrypick master
15 # Alternatively, you can run util/scripts/cross-repo-cherrypick after every
16 # individual cherry-pick.
18 # use $0 --cros to add a stub BUG/BRANCH/TEST block
21 git log -n 1 | grep "^ " | cut -c5-
[all …]
/external/compiler-rt/
DREADME.android2 * README.android describes in high-level the compiler-rt changes that we
4 * - Changes due to Android's build system.
5 * - Changes due to Android's toolchain.
6 * - Changes due to the limitations in Android-based consumer electronics.
8 * Some of them are to-dos. If and when they are done, there will no longer be
11 * The file contains useful hints when we try to resolve future 3-way merge
21 * Cherry-pick on 2014/2/11: https://llvm.org/svn/llvm-project/compiler-rt/trunk@201068 and https://…
31 * Cherry-pick on 2012/07/27: https://llvm.org/svn/llvm-project/compiler-rt/trunk@160853 for ASan (C…
32 * Cherry-pick on 2012/05/23: https://llvm.org/svn/llvm-project/compiler-rt/trunk@157318 for ASan (C…
39 TODO: Switch libbcc to use this version of compiler-rt instead of its own
/external/linux-firmware/
Dupdate_imports.sh3 # Script to cherry-pick 'IMPORT:' CLs. Needed since the Android cherry-picker
12 # http://www.apache.org/licenses/LICENSE-2.0
22 # * Be running in AOSP external/linux-firmware
23 # * git remote add goog sso://googleplex-android/platform/external/linux-firmware
26 set -e
32 rm -f "${aosp_changes}"
33 rm -f "${goog_changes}"
39 git log --reverse --format=%B --grep='^IMPORT:' aosp/main | grep '^Change-Id:' > "${aosp_changes}" …
40 git log --reverse --format=%B --grep='^IMPORT:' goog/main | grep '^Change-Id:' > "${goog_changes}" …
42 declare -A already_picked_dict
[all …]
/external/mesa3d/docs/
Dreleasing.rst5 --------
11 version (Z), while the latter have a non-zero one.
17 Mesa 10.1.0 - 10.1 branch, feature
18 Mesa 10.1.4 - 10.1 branch, bugfix
19 Mesa 12.0.0 - 12.0 branch, feature
20 Mesa 12.0.2 - 12.0 branch, bugfix
25 ----------------
30 See our :doc:`calendar <release-calendar>` for information about how
35 ----------------
37 - Available approximately every three months.
[all …]
/external/perfetto/docs/visualization/
Dperfetto-ui-release-process.md6 - `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/icu/
Dicu_version_upgrade.md4 https://github.com/unicode-org/icu/releases.
10 * See http://site.icu-project.org/repository
11 …* [git-lts](https://git-lfs.github.com/) has to be installed to pull binaries correctly from the g…
12 …* [git-filter-repo](https://github.com/newren/git-filter-repo) for rewriting the `Change-Id` later.
13 2. Generate a github read-access token and setup a local ~/.m2/setting.xml
17 * http://go/repo-init/aosp-main-with-phones
21 * We **rebase** Android-specific patches on the `icu-staging` branch. Then we merge into
24 * We use the **`aosp/upstream-release-cldr** as the mirror of the upstream release branch.
32 lunch aosp_cf_x86_64_phone-trunk_staging-userdebug
35 The build should succeed. Otherwise, your local repo may be broken. Please consider to re-sync.
[all …]

1234567