Home
last modified time | relevance | path

Searched +full:- +full:- +full:no +full:- +full:git +full:- +full:commit (Results 1 – 25 of 401) sorted by relevance

12345678910>>...17

/third_party/skia/m133/bazel/
Ddeps.bzl2 This file is auto-generated from //bazel/deps_parser
8 load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository", "new_git_repository")
15 """A list of native Bazel git rules to download third party git repositories
18 https://bazel.build/rules/lib/repo/git
26 commit = "6d03dfbedda1615c4cba1211f8d81735575209c8",
27 remote = "https://skia.googlesource.com/external/github.com/google/brotli.git",
33 commit = "3f908f3907e532481e4c91d3b814b46869405fe8",
34 remote = "https://dawn.googlesource.com/dawn.git",
39 commit = "65a55c2ba891f6d2492477707f4a2e327a0b40dc",
40 remote = "https://skia.googlesource.com/external/github.com/abseil/abseil-cpp.git",
[all …]
/third_party/rust/rust/src/tools/clippy/book/src/development/infrastructure/
Drelease.md10 1. [Remerge the `beta` branch](#remerge-the-beta-branch)
11 2. [Update the `beta` branch](#update-the-beta-branch)
12 3. [Find the Clippy commit](#find-the-clippy-commit)
13 4. [Tag the stable commit](#tag-the-stable-commit)
14 5. [Update `CHANGELOG.md`](#update-changelogmd)
19 [Rust Forge]: https://forge.rust-lang.org/
25 Clippy commit, that was used by the now stable Rust release, persists in the
31 # Assumes that the local master branch of rust-lang/rust-clippy is up-to-date
32 $ git fetch upstream
33 $ git branch master --contains upstream/beta
[all …]
/third_party/libbpf/scripts/
Dsync-kernel.sh4 echo "USAGE: ./sync-kernel.sh <libbpf-repo> <kernel-repo> <bpf-branch>"
6 …ho "Set BPF_NEXT_BASELINE to override bpf-next tree commit, otherwise read from <libbpf-repo>/CHEC…
7 …echo "Set BPF_BASELINE to override bpf tree commit, otherwise read from <libbpf-repo>/BPF-CHECKPOI…
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 …]
/third_party/skia/m133/third_party/freetype2/
Droll-freetype.sh3 FT_GIT_REPO="https://chromium.googlesource.com/chromium/src/third_party/freetype2.git"
6 FT_BUILD_DIR="$(dirname -- "$0")"
10 if $(git -C "${FT_GIT_DIR}" rev-parse --is-shallow-repository); then
17 …FT_PREVIOUS_REV=$(git grep "${FT_GIT_REPO}" HEAD~1 -- DEPS | sed 's!.*'${FT_GIT_REPO}'@\([[:xdigit…
22 git -C "${FT_GIT_DIR}" fetch &&
23 FT_NEXT_REV=$(git -C "${FT_GIT_DIR}" rev-parse "${FT_GIT_REF}")
27 STEP="roll-deps" &&
28 sed -i'' -e "s!${FT_GIT_REPO}@${FT_PREVIOUS_REV}!${FT_GIT_REPO}@${FT_NEXT_REV}!" DEPS &&
29 tools/git-sync-deps &&
30 git add DEPS
[all …]
/third_party/libuv/
DCONTRIBUTING.md13 $ git clone https://github.com/username/libuv.git
15 $ git remote add upstream https://github.com/libuv/libuv.git
23 API/ABI or affect the run-time behavior of applications get rejected.
39 $ git checkout -b my-feature-branch -t origin/v1.x
50 * Code that is specific to unix-y platforms should be placed in `src/unix`, and
53 * Source code that is Windows-specific goes into `src/win`, and related
62 * Internal, non-static functions should be prefixed with `uv__`.
64 * Use two spaces and no tabs.
68 * Ensure that lines have no trailing whitespace, and use unix-style (LF) line
71 * Use C89-compliant syntax. In other words, variables can only be declared at
[all …]
/third_party/ffmpeg/doc/
Dgit-howto.texi1 \input texinfo @c -*- texinfo -*-
2 @documentencoding UTF-8
4 @settitle Using Git to develop FFmpeg
7 @center @titlefont{Using Git to develop FFmpeg}
16 This document aims in giving some quick references on a set of useful Git
18 provided directly by Git:
21 git --help
22 man git
28 git <command> --help
29 man git-<command>
[all …]
/third_party/libcoap/
DCONTRIBUTE12 * BSD 2-Clause (The BSD 2-Clause License)
14 Contributions made up to 2017-06-01 have been made under the dual
15 license model BSD 2-Clause and GPL v2+ (The GNU General Public License
18 The used VCS for libcoap is Git, the main repository is living on GitHub.
28 GNU GCC and the LLVM C-compiler (CLang) are supported. The Windows VS build
39 No matter if you just have a simple question, some specific problem or
45 https://lists.sourceforge.net/lists/listinfo/libcoap-developers
49 https://sourceforge.net/p/libcoap/mailman/libcoap-developers
55 As written above, libcoap is maintained with the Git tools so you should be
56 familiar with the various git commands.
[all …]
/third_party/elfutils/
DCONTRIBUTING4 git clone git://sourceware.org/git/elfutils.git
7 elfutils-devel@sourceware.org.
8 https://sourceware.org/ml/elfutils-devel/
10 To subscribe send an email to elfutils-devel-subscribe@sourceware.org
11 Or use the form at https://sourceware.org/mailman/listinfo/elfutils-devel
13 Please supply patches using git format-patch or using git send-email.
17 To facilitate tracking of who did what, we've adopted a "sign-off"
21 The sign-off is a simple line at the end of the explanation for the
41 with it, including my sign-off) is maintained indefinitely
46 Signed-off-by: Random J Developer <random@developer.example.org>
[all …]
/third_party/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 …]
Dsubmittingpatches.rst7 ----------------
9 - Patches should not mix code changes with code formatting changes
11 - Code patches should follow Mesa :doc:`coding
13 - Whenever possible, patches should only affect individual Mesa/Gallium
15 - Patches should never introduce build breaks and should be bisectable
16 (see ``Git bisect``.)
17 - Patches should be properly :ref:`formatted <formatting>`.
18 - Patches should be sufficiently :ref:`tested <testing>` before
20 - Patches should be :ref:`submitted <submit>` via a merge request for
26 ----------------
[all …]
/third_party/jerryscript/tools/
Dcheck-signed-off.sh9 # http://www.apache.org/licenses/LICENSE-2.0
20 echo "Usage: $0 [--help] [--tolerant] [--travis]"
25 echo "$0: Check Signed-off-by message of the latest commit"
30 echo " --help print this help message"
31 echo " --tolerant check the existence of the message only but don't"
33 echo " of the commit"
34 echo " --travis perform check in tolerant mode if on Travis CI and not"
37 echo "The last line of every commit message must follow the form of:"
38 echo "'JerryScript-DCO-1.0-Signed-off-by: NAME EMAIL', where NAME and EMAIL must"
39 echo "match the name and email address of the author of the commit (unless in"
[all …]
/third_party/rust/rust/src/tools/clippy/.github/
Ddeploy.sh3 set -ex
6 rm -rf out/master/ || exit 0
10 cp util/gh-pages/index.html out/master
11 cp util/gh-pages/script.js out/master
12 cp util/gh-pages/lints.json out/master
14 if [[ -n $TAG_NAME ]]; then
16 cp -Tr out/master "out/$TAG_NAME"
17 rm -f out/stable
18 ln -s "$TAG_NAME" out/stable
23 cp -r out/master/* out/beta
[all …]
/third_party/rust/rust/compiler/rustc_codegen_gcc/build_sysroot/
Dprepare_sysroot_src.sh2 set -e
8 if [ ! -e $SRC_DIR ]; then
9 echo "Please install rust-src component"
13 rm -rf $DST_DIR
14 mkdir -p $DST_DIR/library
15 cp -r $SRC_DIR/library $DST_DIR/
18 echo "[GIT] init"
19 git init
20 echo "[GIT] add"
21 git add .
[all …]
/third_party/skia/third_party/freetype2/
Droll-freetype.sh3 FT_GIT_REPO=https://chromium.googlesource.com/chromium/src/third_party/freetype2.git
6 FT_BUILD_DIR=$(dirname -- "$0")
10 …FT_PREVIOUS_REV=$(git grep "${FT_GIT_REPO}" HEAD~1 -- DEPS | sed 's!.*'${FT_GIT_REPO}'@\([[:xdigit…
15 git -C ${FT_GIT_DIR} fetch &&
16 FT_NEXT_REV=$(git -C ${FT_GIT_DIR} rev-parse ${FT_GIT_REF})
20 STEP="roll-deps" &&
21 sed -i'' -e "s!${FT_GIT_REPO}@${FT_PREVIOUS_REV}!${FT_GIT_REPO}@${FT_NEXT_REV}!" DEPS &&
22 tools/git-sync-deps &&
23 git add DEPS
31 git -C ${FT_GIT_DIR} cat-file blob ${FT_PREVIOUS_REV}:${FT_INCLUDE} >> ${TMPFILE} &&
[all …]
/third_party/mesa3d/bin/pick/
Dcore.py1 # Copyright © 2019-2020 Intel Corporation
15 # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
49 IS_FIX = re.compile(r'^\s*fixes:\s*([a-f0-9]{6,40})', flags=re.MULTILINE | re.IGNORECASE)
51 IS_CC = re.compile(r'^\s*cc:\s*["\']?([0-9]{2}\.[0-9])?["\']?\s*["\']?([0-9]{2}\.[0-9])?["\']?\s*\<…
53 IS_REVERT = re.compile(r'This reverts commit ([0-9a-f]{40})')
54 IS_BACKPORT = re.compile(r'^\s*backport-to:\s*(\d{2}\.\d),?\s*(\d{2}\.\d)?',
62 git_toplevel = subprocess.check_output(['git', 'rev-parse', '--show-toplevel'],
91 async def commit_state(*, amend: bool = False, message: str = 'Update') -> bool:
92 """Commit the .pick_status.json file."""
95 'git', 'add', pick_status_json.as_posix(),
[all …]
/third_party/curl/docs/
DCONTRIBUTE.md1 <!--
4 SPDX-License-Identifier: curl
5 -->
59 changes](https://curl.se/dev/sourceactivity.html) in git. Just lurking on the
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
92 Preferably, each fix that corrects a problem should be in its own patch/commit
93 with its own description/commit message stating exactly what they correct so
[all …]
/third_party/ninja/
DRELEASING4 1. Run afl-fuzz for a day or so and run ninja_test
5 2. Consider sending a heads-up to the ninja-build mailing list first
7 4. Update src/version.cc with new version (with ".git"), then
8 git commit -am 'mark this 1.5.0.git'
9 5. git checkout release; git merge master
12 8. commit, tag, push (don't forget to push --tags)
13 git commit -am v1.5.0; git push origin release
14 git tag v1.5.0; git push --tags
15 # Push the 1.5.0.git change on master too:
16 git checkout master; git push origin master
[all …]
DRELEASING.md4 1. Run afl-fuzz for a day or so and run ninja_test
5 2. Consider sending a heads-up to the ninja-build mailing list first
7 4. Update src/version.cc with new version (with ".git"), then
9 git commit -am 'mark this 1.5.0.git'
11 5. git checkout release; git merge master
14 8. commit, tag, push (don't forget to push --tags)
16 git commit -am v1.5.0; git push origin release
17 git tag v1.5.0; git push --tags
18 # Push the 1.5.0.git change on master too:
19 git checkout master; git push origin master
[all …]
/third_party/rust/crates/lazycell/
DCONTRIBUTING.md7 2. Clone your fork (`git clone https://github.com/$YOUR_USERNAME/lazycell && cd lazycell`)
8 3. Create a new branch (`git checkout -b new-branch`)
10 5. Commit your changes (`git commit -am "your message"`)
12 [conventional changelog format][conventional-changelog-format], so that we can
13 easily update the `CHANGELOG.md` using [clog][clog-cli].
16 * Format your commit subject line using the following format:
18 - `feat` - A new feature
19 - `imp` - An improvement to an existing feature
20 - `perf` - A performance improvement
21 - `docs` - Changes to documentation only
[all …]
/third_party/mesa3d/.gitlab-ci/fossils/
Dfossils.sh5 FOSSILS_SCRIPT_DIR="$(dirname "$(readlink -f "$0")")"
6 FOSSILS_YAML="$(readlink -f "$1")"
12 local commit="$2"
13 rm -rf fossils-db
14 git clone --no-checkout "$repo" fossils-db
15 (cd fossils-db || return; git reset "$commit" || git reset "origin/$commit")
21 --file "$FOSSILS_YAML" "$@"
26 rm -rf .clean_git
27 cp -R .git .clean_git
32 rm -rf .git
[all …]
/third_party/openssl/test/
DREADME-external.md14 First checkout the `PYCA/Cryptography` module into `./pyca-cryptography` using:
16 $ git submodule update --init
20 $ ./config shared enable-external-tests
29 ------------------------------
32 other crypto implementations so are not relevant. Currently no tests fail.
40 You will need a git checkout of krb5 at the top level:
42 $ git clone https://github.com/krb5/krb5
44 krb5's master has to pass this same CI, but a known-good version is
45 krb5-1.15.1-final if you want to be sure.
48 $ git checkout krb5-1.15.1-final
[all …]
/third_party/libinput/
DCODING_STYLE.md3 - Indentation in tabs, 8 characters wide, spaces after the tabs where
9 - Max line width 80ch, do not break up printed strings though
11 - Break up long lines at logical groupings, one line for each logical group
27 - Function declarations: return type on separate line, {} on separate line,
45 - `/* comments only */`, no `// comments`
47 - `variable_name`, not `VariableName` or `variableName`. same for functions.
49 - no typedefs of structs, enums, unions
51 - if it generates a compiler warning, it needs to be fixed
52 - if it generates a static checker warning, it needs to be fixed or
55 - declare variables when they are used first and try to keep them as local as possible.
[all …]
/third_party/rust/rust/src/tools/clippy/clippy_dev/src/setup/
Dgit_hook.rs6 /// Rusts setup uses `git rev-parse --git-common-dir` to get the root directory of the repo.
10 const REPO_GIT_DIR: &str = ".git";
11 const HOOK_SOURCE_FILE: &str = "util/etc/pre-commit.sh";
12 const HOOK_TARGET_FILE: &str = ".git/hooks/pre-commit";
19 // So a little bit of a funny story. Git on unix requires the pre-commit file in install_hook()
24 // setup script. Git saves the `execute` flag when syncing files. This means in install_hook()
30 println!("info: the hook can be removed with `cargo dev remove git-hook`"); in install_hook()
31 println!("git hook successfully installed"); in install_hook()
37 fn check_precondition(force_override: bool) -> bool { in check_precondition()
42 // Make sure that we can find the git repository in check_precondition()
[all …]
/third_party/rust/rust/.github/workflows/
Ddependencies.yml3 ---
8 - cron: '0 0 * * Sun'
27 not-waiting-on-bors:
28 if: github.repository_owner == 'rust-lang'
29 name: skip if S-waiting-on-bors
30 runs-on: ubuntu-latest
32 - env:
37 JSON=$(gh pr view cargo_update --repo $GITHUB_REPOSITORY --json labels,state || exit 0)
38 STATE=$(echo "$JSON" | jq -r '.state')
39 WAITING_ON_BORS=$(echo "$JSON" | jq '.labels[] | any(.name == "S-waiting-on-bors"; .)')
[all …]
/third_party/icu/tools/commit-checker/
Dcheck.py15 from git import Repo
20 ICUCommit = namedtuple("ICUCommit", ["issue_id", "commit"])
37 # <https://unicode-org.atlassian.net/rest/api/2/resolution>
52 # <https://unicode-org.atlassian.net/rest/api/2/issuetype>
57 # <https://unicode-org.atlassian.net/rest/api/2/status>
99 "--rev-range",
100 …help = "A git revision range; see https://git-scm.com/docs/gitrevisions. Should be the two-dot ran…
104 "--repo-root",
109 "--jira-hostname",
111 default = "unicode-org.atlassian.net"
[all …]

12345678910>>...17