Searched +full:git +full:- +full:tool (Results 1 – 25 of 725) sorted by relevance
12345678910>>...29
| /external/deqp-deps/SPIRV-Tools/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0 19 set -e 21 set -x 23 # This is required to run any git command in the docker since owner will 26 git config --global --add safe.directory $ROOT_DIR 30 using python-3.12 33 using clang-10.0.0 35 using gcc-9 42 if [[ -d "$dir" ]]; then 43 rm -fr "$dir" [all …]
|
| /external/angle/third_party/spirv-tools/src/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0 19 set -e 21 set -x 23 # This is required to run any git command in the docker since owner will 26 git config --global --add safe.directory $ROOT_DIR 30 using python-3.12 33 using clang-13.0.1 35 using gcc-13 42 if [[ -d "$dir" ]]; then 43 rm -fr "$dir" [all …]
|
| /external/swiftshader/third_party/SPIRV-Tools/kokoro/scripts/linux/ |
| D | build-docker.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0 19 set -e 21 set -x 23 # This is required to run any git command in the docker since owner will 26 git config --global --add safe.directory $ROOT_DIR 31 using clang-10.0.0 33 using gcc-9 40 if [[ -d "$dir" ]]; then 41 rm -fr "$dir" 46 if [ $TOOL != "cmake-smoketest" ]; then [all …]
|
| /external/trusty/arm-trusted-firmware/tools/tlc/ |
| D | pyproject.toml | 1 # Poetry pyproject.toml: https://python-poetry.org/docs/pyproject/ 2 [build-system] 4 build-backend = "poetry.core.masonry.api" 6 [tool.poetry] 9 description = "Transfer List Compiler (TLC) is a Python-based CLI for efficiently handling transfer… 10 authors = ["Arm Ltd <tf-a@lists.trustedfirmware.org>"] 11 license = "BSD-3" 12 repository = "https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/" 13 homepage = "https://trustedfirmware-a.readthedocs.io/en/latest/index.html" 15 # Keywords description https://python-poetry.org/docs/pyproject/#keywords [all …]
|
| /external/v4l-utils/ |
| D | README.md | 1 # v4l-utils 6 You can always find the latest development v4l-utils in the git repo: 7 [http://git.linuxtv.org/v4l-utils.git](http://git.linuxtv.org/v4l-utils.git). 10 [http://linuxtv.org/downloads/v4l-dvb-apis/](http://linuxtv.org/downloads/v4l-dvb-apis/). 12 Any questions/remarks/patches can be sent to the linux-media mailinglist. See 16 There is also a wiki page for the v4l-utils: 17 [https://linuxtv.org/wiki/index.php/V4l-utils](https://linuxtv.org/wiki/index.php/V4l-utils). 21 v4l-utils uses the meson build system. 23 A number of packages is required to fully build v4l-utils. The first step is to 27 packages with `apt-get` or `aptitude`: [all …]
|
| /external/sdv/vsomeip/third_party/boost/process/.circleci/ |
| D | config.yml | 6 - BOOST_LIBRARY=process 7 - CXX_STANDARD=gnu++11 9 - image: gcc:7 11 - checkout 12 - run: 15 echo 'export BOOST="$HOME/boost-local"' >> $BASH_ENV 22 HOME_SED_=$(echo $HOME | sed -e 's/\//\\\//g') 24 - run: 27 apt-get update -yqq 28 apt-get install git curl valgrind -y [all …]
|
| /external/toolchain-utils/go/patch/go-1.10.3/ |
| D | go3.patch | 1 diff --git test/fixedbugs/bug302.go test/fixedbugs/bug302.go 3 --- test/fixedbugs/bug302.go 5 @@ -1,5 +1,5 @@ 7 -// run 11 // Use of this source code is governed by a BSD-style 12 @@ -8,16 +8,27 @@ 33 - run("go", "tool", "compile", filepath.Join("fixedbugs", "bug302.dir", "p.go")) 34 - run("go", "tool", "pack", "grc", "pp.a", "p.o") 35 - run("go", "tool", "compile", "-I", ".", filepath.Join("fixedbugs", "bug302.dir", "main.go")) 37 + run(goCmd(), "tool", "compile", filepath.Join("fixedbugs", "bug302.dir", "p.go")) [all …]
|
| /external/toolchain-utils/go/patch/go-1.11.2/ |
| D | go3.patch | 1 diff --git test/fixedbugs/bug302.go test/fixedbugs/bug302.go 3 --- test/fixedbugs/bug302.go 5 @@ -1,5 +1,5 @@ 7 -// run 11 // Use of this source code is governed by a BSD-style 12 @@ -8,16 +8,28 @@ 34 - run("go", "tool", "compile", filepath.Join("fixedbugs", "bug302.dir", "p.go")) 35 - run("go", "tool", "pack", "grc", "pp.a", "p.o") 36 - run("go", "tool", "compile", "-I", ".", filepath.Join("fixedbugs", "bug302.dir", "main.go")) 38 + run(goCmd(), "tool", "compile", filepath.Join("fixedbugs", "bug302.dir", "p.go")) [all …]
|
| /external/rust/android-crates-io/extra_versions/crates/clap/examples/ |
| D | git.md | 1 Git is an example of several common subcommand patterns. 5 $ git 7 git 11 git[EXE] <SUBCOMMAND> 14 -h, --help Print help information 23 $ git help 24 git 28 git[EXE] <SUBCOMMAND> 31 -h, --help Print help information 40 $ git help add [all …]
|
| D | git-derive.md | 3 Git is an example of several common subcommand patterns. 7 $ git-derive 9 git 13 git-derive[EXE] <SUBCOMMAND> 16 -h, --help Print help information 25 $ git-derive help 26 git 30 git-derive[EXE] <SUBCOMMAND> 33 -h, --help Print help information 42 $ git-derive help add [all …]
|
| /external/libwebm/common/ |
| D | common.sh | 5 ## Use of this source code is governed by a BSD-style license 11 set -e 37 # the tool being tested to return a successful exit code can be passed as 40 tool="$1" 43 if ! eval "${tool}" ${tool_args} > /dev/null 2>&1; then 44 elog "${tool} must be in your path." 49 # Echoes git describe output for the directory specified by $1 to stdout. 53 echo $(git -C "${git_dir}" describe) 56 # Echoes current git revision for the directory specifed by $1 to stdout. 60 echo $(git -C "${git_dir}" rev-parse HEAD)
|
| /external/clang/docs/ |
| D | LibASTMatchersTutorial.rst | 5 This document is intended to show how to build a useful source-to-source 6 translation tool based on Clang's `LibTooling <LibTooling.html>`_. It is 20 repositories, but we'll be accessing them through the git mirror. For 24 .. code-block:: console 26 mkdir ~/clang-llvm && cd ~/clang-llvm 27 git clone http://llvm.org/git/llvm.git 29 git clone http://llvm.org/git/clang.git 31 git clone http://llvm.org/git/clang-tools-extra.git extra 33 Next you need to obtain the CMake build system and Ninja build tool. You 37 .. code-block:: console [all …]
|
| D | ClangTools.rst | 7 Clang as their compiler. These tools provide developer-oriented 13 side-project so that developers who don't want or need to build them 19 - With Subversion: 21 - ``cd llvm/tools/clang/tools`` 22 - ``svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk extra`` 24 - Or with Git: 26 - ``cd llvm/tools/clang/tools`` 27 - ``git clone http://llvm.org/git/clang-tools-extra.git extra`` 29 This document describes a high-level overview of the organization of 32 document is currently focused on Clang and Clang Tool developers, not on [all …]
|
| /external/cronet/tot/third_party/rust/chromium_crates_io/vendor/clap-4.5.21/examples/ |
| D | git.md | 1 Git is an example of several common subcommand patterns. 5 $ git 9 Usage: git[EXE] <COMMAND> 20 -h, --help Print help 22 $ git help 25 Usage: git[EXE] <COMMAND> 36 -h, --help Print help 38 $ git help add 41 Usage: git[EXE] add <PATH>... 47 -h, --help Print help [all …]
|
| D | git-derive.md | 3 Git is an example of several common subcommand patterns. 7 $ git-derive 11 Usage: git-derive[EXE] <COMMAND> 22 -h, --help Print help 24 $ git-derive help 27 Usage: git-derive[EXE] <COMMAND> 38 -h, --help Print help 40 $ git-derive help add 43 Usage: git-derive[EXE] add <PATH>... 49 -h, --help Print help [all …]
|
| /external/cronet/stable/third_party/rust/chromium_crates_io/vendor/clap-4.5.21/examples/ |
| D | git.md | 1 Git is an example of several common subcommand patterns. 5 $ git 9 Usage: git[EXE] <COMMAND> 20 -h, --help Print help 22 $ git help 25 Usage: git[EXE] <COMMAND> 36 -h, --help Print help 38 $ git help add 41 Usage: git[EXE] add <PATH>... 47 -h, --help Print help [all …]
|
| D | git-derive.md | 3 Git is an example of several common subcommand patterns. 7 $ git-derive 11 Usage: git-derive[EXE] <COMMAND> 22 -h, --help Print help 24 $ git-derive help 27 Usage: git-derive[EXE] <COMMAND> 38 -h, --help Print help 40 $ git-derive help add 43 Usage: git-derive[EXE] add <PATH>... 49 -h, --help Print help [all …]
|
| /external/rust/android-crates-io/crates/clap/examples/ |
| D | git.md | 1 Git is an example of several common subcommand patterns. 5 $ git 9 Usage: git[EXE] <COMMAND> 20 -h, --help Print help 22 $ git help 25 Usage: git[EXE] <COMMAND> 36 -h, --help Print help 38 $ git help add 41 Usage: git[EXE] add <PATH>... 47 -h, --help Print help [all …]
|
| D | git-derive.md | 3 Git is an example of several common subcommand patterns. 7 $ git-derive 11 Usage: git-derive[EXE] <COMMAND> 22 -h, --help Print help 24 $ git-derive help 27 Usage: git-derive[EXE] <COMMAND> 38 -h, --help Print help 40 $ git-derive help add 43 Usage: git-derive[EXE] add <PATH>... 49 -h, --help Print help [all …]
|
| /external/tensorflow/tensorflow/tools/ci_build/ |
| D | sizetrack_helper.py | 8 # http://www.apache.org/licenses/LICENSE-2.0 16 r"""Used for Google-internal artifact size tracking. 18 See go/tf-devinfra/sizetrack. 23 --artifact=ARTIFACT, or --manual_bytes=MANUAL_BYTES 24 --artifact_id=ARTIFACT_ID \ 25 --team=TEAM \ 42 1. Current directory is a git repository 43 2. CL-based commits have a PiperOrigin-RevId trailer. This is the case 44 for any use of Copybara Single-source-of-truth, e.g. TensorFlow. 61 "--project", [all …]
|
| /external/trusty/arm-trusted-firmware/tools/cot_dt2c/ |
| D | pyproject.toml | 1 # Poetry pyproject.toml: https://python-poetry.org/docs/pyproject/ 2 [build-system] 4 build-backend = "poetry.core.masonry.api" 6 [tool.poetry] 9 description = "CoT-dt2c Tool is a python script to convert CoT DT file into corresponding C file" 10 authors = ["Arm Ltd <tf-a@lists.trustedfirmware.org>"] 11 license = "BSD-3" 12 repository = "https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/" 13 homepage = "https://trustedfirmware-a.readthedocs.io/en/latest/index.html" 17 "Development Status :: 3 - Alpha", [all …]
|
| /external/openthread/tools/gerrit/ |
| D | README.md | 1 # git-squash-merge tool 3 `git-squash-merge` is a bash script to help squash merge a given branch into the current branch. Th… 10 git-squash-merge [--no-list] [--no-commit] <branch> [<commit msg>]" 15 - `<branch>` specifies the name of branch to merge into current branch. 16 - `<commit msg>` is an optional parameter specifying text to add to the commit message. 20 - `--no-list` when used the commit message will not include the list of squashed commits. 21 - `--no-commit` when used, the tool squashes and stages the changes but does not commit" 26 ~/sw/openthread $ ./tools/gerrit/git-squash-merge.sh github/master "OpenThread GitHub sync" 29 Date: Tue Aug 14 14:53:33 2018 -0700 39 7be61df6e [message-info] remove unnecessary memset initialization (#2937) [all …]
|
| /external/sdk-platform-java/.githooks/ |
| D | pre-commit | 3 # Pre-commit Git checks. 5 # ln -s .githooks/pre-commit .git/hooks/pre-commit 21 echo -e "$BOLD $BACK_BLUE $WHITE Precommit:\t $BACK_RED Changes NOT committed. $UNSET" 22 …echo -e "$BOLD $BACK_BLUE $WHITE Precommit:\t $BACK_RED $WHITE $ERR_MSG $BACK_BLUE $HELP_MSG $UNSE… 27 echo -e "$BOLD $BACK_BLUE $WHITE Precommit:\t $STATUS_MSG $UNSET" 31 …echo -e "$BOLD $BACK_BLUE $WHITE Precommit:\t $BACK_GREEN $WHITE SUCCESS. $UNSET All checks passed… 37 if [ $? -ne 0 ]; 48 if [ $? -ne 0 ]; 50 echo_status "addlicense tool is not yet installed, downloading it now." 57 echo_status "Setting up tool to fix Bazel format" [all …]
|
| /external/robolectric/scripts/ |
| D | README.md | 1 # Robolectric build-android.sh tutorial 5 … you to run the `build-android.sh` script in the Robolectric repository, resulting in the correspo… 8 Repo is a tool that makes it easier to work with Git in the context of Android. For more informatio… 16 Download the Repo tool and ensure that it is executable: 18 $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo 25 … to hold your working files. If you're using MacOS, this has to be on a case-sensitive filesystem.… 31 Configure git with your real name and email address. To use the Gerrit code-review tool, you will n… 33 $ git config --global user.name "Your Name" 34 $ git config --global user.email "you@example.com" 40 $ sudo apt-get install git-core gnupg gnupg-agent flex bison gperf build-essential \ [all …]
|
| /external/coreboot/util/docker/coreboot.org-status/board-status.html/ |
| D | README | 1 Tool to publish board-status data to the website 4 This tool parses the board-status repository (and the coreboot repository as 6 in board-status. 9 https://coreboot.org/status/board-status.html 12 ---------- 13 When modifying the tool, or when publishing the results elsewhere, you 14 might want to run it yourself. You'll need the board-status and the coreboot 17 To build the tool, run the following commands 24 $ ./board-status.html \ 25 -board-status-dir .../board-status.git \ [all …]
|
12345678910>>...29