Home
last modified time | relevance | path

Searched +full:commit +full:- +full:message (Results 1 – 25 of 577) sorted by relevance

12345678910>>...24

/third_party/mesa3d/bin/pick/
Dcore_test.py1 # Copyright © 2019-2020 Intel Corporation
36 def unnominated_commit(self) -> 'core.Commit':
37 return core.Commit('abc123', 'sub: A commit', main_sha='45678')
40 def nominated_commit(self) -> 'core.Commit':
41 return core.Commit('abc123', 'sub: A commit', True,
46 def test_not_nominated(self, unnominated_commit: 'core.Commit'): argument
49 assert v == {'sha': 'abc123', 'description': 'sub: A commit', 'nominated': False,
53 def test_nominated(self, nominated_commit: 'core.Commit'): argument
57 'description': 'sub: A commit',
66 def test_not_nominated(self, unnominated_commit: 'core.Commit'): argument
[all …]
Dcore.py1 # Copyright © 2019-2020 Intel Corporation
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."""
104 cmd = ['--amend', '--no-edit']
106 cmd = ['--message', f'.pick_status.json: {message}']
[all …]
/third_party/skia/experimental/documentation/
Dgerrit.md1 Using Gerrit without git-cl
5 -----
9 This command sets up a Git commit-message hook to add a unique Change-Id to
10 each commit. Gerrit only accepts changes with a Change-Id and uses it to
13 experimental/tools/set-change-id-hook
20 git remote set-url origin 'https://skia.googlesource.com/skia.git'
24 --------------
26 Go to [skia.googlesource.com/new-password](https://skia.googlesource.com/new-password)
31 -----------------
35 git checkout -b TOPIC
[all …]
/third_party/skia/m133/experimental/documentation/
Dgerrit.md1 Using Gerrit without git-cl
5 -----
9 This command sets up a Git commit-message hook to add a unique Change-Id to
10 each commit. Gerrit only accepts changes with a Change-Id and uses it to
13 experimental/tools/set-change-id-hook
20 git remote set-url origin 'https://skia.googlesource.com/skia.git'
24 --------------
26 Go to [skia.googlesource.com/new-password](https://skia.googlesource.com/new-password)
31 -----------------
35 git checkout -b TOPIC
[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/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/liburing/.github/
Dpull_request_template.md2 <!-- Explain your changes here... -->
4 ----
5 ## git request-pull output:
7 <!-- START REPLACE ME -->
10 git remote add axboe-tree https://github.com/axboe/liburing
11 git fetch axboe-tree
12 git request-pull axboe-tree/master your_fork_URL your_branch_name
14 Then replace this with the output of `git request-pull` command.
16 <!-- END REPLACE ME -->
18 ----
[all …]
/third_party/rust/crates/clap/examples/
Dgit-derive.md7 $ git-derive
11 Usage: git-derive[EXE] <COMMAND>
19 help Print this message or the help of the given subcommand(s)
22 -h, --help Print help
24 $ git-derive help
27 Usage: git-derive[EXE] <COMMAND>
35 help Print this message or the help of the given subcommand(s)
38 -h, --help Print help
40 $ git-derive help add
43 Usage: git-derive[EXE] add <PATH>...
[all …]
Dgit.md17 help Print this message or the help of the given subcommand(s)
20 -h, --help Print help
33 help Print this message or the help of the given subcommand(s)
36 -h, --help Print help
47 -h, --help Print help
63 -h, --help Print help
72 $ git stash -h
80 help Print this message or the help of the given subcommand(s)
83 -m, --message <MESSAGE>
84 -h, --help Print help
[all …]
/third_party/jerryscript/.github/
Dpull_request_template.md5 - Changes are in a separate branch, not in master.
6 - The branch contains only one commit on top of master (if not, squash them into
7 one commit).
8 - The commit has a descriptive commit message with a concise title (first line).
9 - The commit message contains `fixes #XXXX` or `closes #XXXX` to auto-close the
11 - Tests for the changes have been added (for bug fixes / features).
12 - Documentation has been added / updated (if applicable).
13 - All new and existing tests passed locally (if not, fix them first and amend
14 the commit).
/third_party/lz4/tests/
Dtest-lz4-speed.py4 # Copyright (c) 2016-2020, Przemyslaw Skibinski, Yann Collet, Facebook, Inc.
7 # This source code is licensed under the BSD-style license found in the
13 # - doesn't support filenames with spaces
14 # - dir1/lz4 and dir2/lz4 will be merged in a single results file
24 script_version = 'v1.7.2 (2016-11-08)'
45 print(time.strftime("%Y/%m/%d %H:%M:%S") + ' - ' + text)
53 stderr_lines = stderr_lines.decode("utf-8")
54 stdout_lines = stdout_lines.decode("utf-8")
82 execute('mutt -s "' + topic + '" ' + emails + ' < ' + logFileName, verbose)
84 execute('mail -s "' + topic + '" ' + emails + ' < ' + logFileName, verbose)
[all …]
/third_party/mesa3d/bin/
Dcommit_in_branch.py8 def print_(args: argparse.Namespace, success: bool, message: str) -> None:
33 s += message
41 def is_commit_valid(commit: str) -> bool:
42 ret = subprocess.call(['git', 'cat-file', '-e', commit],
48 def branch_has_commit(upstream_branch: str, commit: str) -> bool:
50 Returns True if the commit is actually present in the branch
52 ret = subprocess.call(['git', 'merge-base', '--is-ancestor',
53 commit, upstream_branch],
59 def branch_has_backport_of_commit(upstream_branch: str, commit: str) -> str:
61 Returns the commit hash if the commit has been backported to the branch,
[all …]
/third_party/pulseaudio/.gitlab/merge_request_templates/
DGuidelines.md16 For non-trivial patches, we meet biweekly on IRC to discuss and prioritise
31 ## Commit messagse
33 We follow the standard git commit message format of a summary on the first line
35 line, followed by a detailed commit message. An additional line at the end may
38 The first line is usually a short description of "what" your commit does, and
39 the rest of the message describes the "why", along with any additional
43 If you need to describe the "how" of the commit, that is usually best
46 Commit messages are prefixed with the subsystem being affected. Your best bet
47 to figure out what is appropriate is to look at previous commit messages. An
53 Some gaming sound cards have custom profiles with analog-game and
[all …]
/third_party/pulseaudio/
DCONTRIBUTING.md16 For non-trivial patches, we meet biweekly on IRC to discuss and prioritise
31 ## Commit messages
33 We follow the standard git commit message format of a summary on the first line
35 line, followed by a detailed commit message. An additional line at the end may
38 The first line is usually a short description of "what" your commit does, and
39 the rest of the message describes the "why", along with any additional
43 If you need to describe the "how" of the commit, that is usually best
46 Commit messages are prefixed with the subsystem being affected. Your best bet
47 to figure out what is appropriate is to look at previous commit messages. An
53 Some gaming sound cards have custom profiles with analog-game and
[all …]
/third_party/elfutils/
DCONTRIBUTING7 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>
52 git commit --signoff will add such a Signed-off-by line at the end of
[all …]
/third_party/skia/third_party/externals/dawn/docs/
Dcontributing.md25 Dawn's contributions are submitted and reviewed on [Dawn's Gerrit](https://dawn-review.googlesource…
31 - `refs/for/<branch>` (most commonly `refs/for/main`) is a branch that anyone
34 - `refs/changes/00/<change number>/<patchset>` is a branch that corresponds to
42 when connecting to the remote. To get the `.gitcookies`, log-in to [Dawn's Gerrit](https://dawn-rev…
43 and browse to the [new-password](https://dawn.googlesource.com/new-password)
46 #### Set up the commit-msg hook
48 Gerrit associates commits to CLs based on a `Change-Id:` tag in the commit
49 message. Each push with commits with a `Change-Id:` will update the
52 To add the `commit-msg` hook that will automatically add a `Change-Id:` to your
53 commit messages, run the following command:
[all …]
/third_party/rust/rust/src/tools/clippy/util/
Dfetch_prs_between.sh4 # together with the full commit message
7 # exclude the non-user facing changes like 'rustup' PRs, typo fixes, etc.
14 …n $(git log --oneline --grep "Merge #" --grep "Merge pull request" --grep "Auto merge of" --grep "…
15 id=$(echo "$pr" | rg -o '#[0-9]{3,5}' | cut -c 2-)
16 commit=$(echo "$pr" | cut -d' ' -f 1)
17 message=$(git --no-pager show --pretty=medium "$commit")
18 if [[ -n $(echo "$message" | rg "^[\s]{4}changelog: [nN]one\.*$") ]]; then
22 echo "URL: https://github.com/rust-lang/rust-clippy/pull/$id"
23 echo "Markdown URL: [#$id](https://github.com/rust-lang/rust-clippy/pull/$id)"
24 echo "$message"
[all …]
/third_party/mbedtls/scripts/
Dassemble_changelog.py5 Add changelog entries to the first level-2 section.
6 Create a new level-2 section for unreleased changes if needed.
7 Remove the input files unless --keep-entries is specified.
9 In each level-3 section, entries are sorted in chronological order
12 the merge commit that brought the commit that created the file into
15 of the commit that adds them.
22 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
35 def __init__(self, filename, line_number, message, *args, **kwargs): argument
36 message = '{}:{}: {}'.format(filename, line_number,
37 message.format(*args, **kwargs))
[all …]
/third_party/rust/crates/lazycell/
DCONTRIBUTING.md8 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:
17 `TYPE(COMPONENT): MESSAGE` where `TYPE` is one of the following:
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/libdrm/
DCONTRIBUTING.rst5 ------------------
7 Patches should be sent to dri-devel@lists.freedesktop.org, using git
8 send-email. For patches only touching driver specific code one of the driver
9 mailing lists (like amd-gfx@lists.freedesktop.org) is also appropriate. See git
12 http://git-scm.com/documentation
14 Since dri-devel is a very busy mailing list please use --subject-prefix="PATCH
17 git config --local format.subjectprefix "PATCH libdrm"
19 The first line of a commit message should contain a prefix indicating what part
25 The body of the commit message should describe what the patch changes and why,
27 writing commit messages, see:
[all …]
/third_party/nghttp2/
Dgit-clang-format3 #===- git-clang-format - ClangFormat Git Integration ---------*- python -*--===#
10 #===------------------------------------------------------------------------===#
13 clang-format git integration
16 This file provides a clang-format integration for git. Put it somewhere in your
17 path and ensure that it is executable. Then, "git clang-format" will invoke
18 clang-format on the changes in current files or a specific commit.
21 git clang-format -h
35 usage = 'git clang-format [OPTIONS] [<commit>] [--] [<file>...]'
38 Run clang-format on all lines that differ between the working directory
39 and <commit>, which defaults to HEAD. Changes are only applied to the working
[all …]
/third_party/rust/rust/src/tools/
Dpublish_toolstate.py2 # -*- coding: utf-8 -*-
6 # It gets called from `src/ci/publish_toolstate.sh` when a new commit lands on `master`
30 # These should be collaborators of the rust-lang/rust repository (with at least
36 'rust-by-example': {'marioidival'},
37 'embedded-book': {'adamgreig', 'andre-richter', 'jamesmunns', 'therealprof'},
38 'edition-guide': {'ehuss'},
39 'rustc-dev-guide': {'spastorino', 'amanjeev', 'JohnTitor'},
43 'book': ['C-bug'],
44 'nomicon': ['C-bug'],
45 'reference': ['C-bug'],
[all …]
/third_party/grpc/
DCONTRIBUTING.md4 organization's [governance rules](https://github.com/grpc/grpc-community/blob/master/governance.md)
5 and [contribution guidelines](https://github.com/grpc/grpc-community/blob/master/CONTRIBUTING.md) b…
8 howto](https://help.github.com/articles/about-pull-requests/)
22 … in [Building gRPC C++: Clone the repository](BUILDING.md#clone-the-repository-including-submodule…
32 - Prepare your development environment based on language-specific instructions in `src/YOUR-LANGUAG…
33 - The language-specific instructions might involve installing C/C++ prerequisites listed in
34 …[Building gRPC C++: Prerequisites](BUILDING.md#pre-requisites). This is because gRPC implementatio…
36 - Run
38 python tools/run_tests/run_tests.py -l YOUR_LANGUAGE --build_only
40 - To also run all the unit tests after building
[all …]
/third_party/libabigail/
DCOMMIT-LOG-GUIDELINES1 Git commit messages format
4 The principle of the git commit log is to document at least the
5 *what*; in English. That is redundant with the commit diff, yes. But
6 that redundancy does help in understanding the commit diff better. If
7 appropriate, the commit log can also document the *why*, but only if
8 it does so by respecting the format of the commit log. The reason why
9 we are so strict about the format is that the commit log is later
15 The first line of a git commit message should start at column 1, with
17 commit. If the commit relates to a bug filed into bugzilla, the line
21 Bug <number-of-the-bug> This is a great commit
[all …]
/third_party/skia/m133/third_party/externals/libwebp/
DCONTRIBUTING.md22 https://chromium-review.googlesource.com for this purpose.
34 2. Copy the commit-msg script into ./git/hooks (this will add an ID to all of
38 …curl -Lo .git/hooks/commit-msg https://chromium-review.googlesource.com/tools/hooks/commit-msg && …
44 4. Choose a short and representative commit message:
47 git commit -a -m "Set commit message here"
53 git push https://chromium-review.googlesource.com/webm/libwebp HEAD:refs/for/main
56 Go to https://chromium-review.googlesource.com to view your patch and
60 [WebM Project page](https://www.webmproject.org/code/contribute/submitting-patches/)
67 `clang-format --style=Google`, though this project doesn't use the tool to
71 [cmake-format](https://cmake-format.readthedocs.io/en/latest/). `cmake-format
[all …]

12345678910>>...24