Home
last modified time | relevance | path

Searched refs:commit (Results 1 – 24 of 24) sorted by relevance

/trusted-firmware-a-3.4.0/tools/conventional-changelog-tf-a/
Dindex.js76 notes: notes.filter(note => section.scopes?.includes(note.commit.scope)),
95 … !flattenedSections.some(section => section.scopes?.includes(note.commit.scope))),
110 commits: commits.filter(commit => section.scopes?.includes(commit.scope)),
128 commits: commitGroup.commits.filter(commit =>
129 !flattenedSections.some(section => section.scopes?.includes(commit.scope))),
168 writerOpts.transform = function (commit, context) { argument
174 commit.notes.forEach(note => {
182 return ccWriterOptsTransform(commit, context);
/trusted-firmware-a-3.4.0/tools/conventional-changelog-tf-a/templates/
Dnote.hbs3 **See:** {{#with commit }}{{> commit root=@root showScope=../showScope }}{{/with}}
Dcommit-section.hbs6 {{#tf-a-mdlist 0}}{{> commit root=@root showScope=../topLevel }}{{/tf-a-mdlist ~}}
13 …{{#tf-a-mdlist 0}}{{> tf-a-commit-section root=@root header=(tf-a-concat "**" title "**") }}{{/tf-…
Dtemplate.hbs8 {{> tf-a-commit-section root=@root header=(tf-a-concat "### " title) topLevel=true }}
/trusted-firmware-a-3.4.0/docs/process/
Dindex.rst11 commit-style
Dcommit-style.rst4 When writing commit messages, please think carefully about the purpose and scope
8 keep a more accurate changelog. You may use Markdown in commit messages.
10 A good commit message provides all the background information needed for
29 To briefly summarize, commit messages are expected to be of the form:
39 The following example commit message demonstrates the use of the
91 in the :ref:`prerequisites <Prerequisites>` guide to validate commit messages
147 Ensure that each commit also has a unique ``Change-Id:`` line. If you have
149 or clone the repository using the "`Clone with commit-msg hook`" clone method,
Dcontributing.rst40 - Avoid long commit series. If you do have a long series, consider whether
59 (and nothing else) in the last commit of the series. Otherwise, include
60 the documentation changes within the single commit.
157 - If the changes are not based on a sufficiently-recent commit, or if they
Dcode-review-guidelines.rst201 posted via the commit message or on the mailing list.
/trusted-firmware-a-3.4.0/plat/imx/common/include/sci/svc/misc/
Dsci_misc_api.h326 void sc_misc_seco_build_info(sc_ipc_t ipc, uint32_t *version, uint32_t *commit);
376 void sc_misc_build_info(sc_ipc_t ipc, uint32_t *build, uint32_t *commit);
/trusted-firmware-a-3.4.0/.husky/
Dcommit-msg.gerrit190 git hash-object -t commit --stdin
/trusted-firmware-a-3.4.0/plat/imx/common/sci/svc/misc/
Dmisc_rpc_clnt.c226 void sc_misc_seco_build_info(sc_ipc_t ipc, uint32_t *version, uint32_t *commit) in sc_misc_seco_build_info() argument
240 if (commit != NULL) in sc_misc_seco_build_info()
241 *commit = RPC_U32(&msg, 4U); in sc_misc_seco_build_info()
304 void sc_misc_build_info(sc_ipc_t ipc, uint32_t *build, uint32_t *commit) in sc_misc_build_info() argument
318 if (commit != NULL) in sc_misc_build_info()
319 *commit = RPC_U32(&msg, 4U); in sc_misc_build_info()
/trusted-firmware-a-3.4.0/docs/security_advisories/
Dsecurity-advisory-tfv-5.rst55 .. _Commit e290a8fcbc: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=e290a…
56 .. _Commit c3e8b0be9b: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=c3e8b…
Dsecurity-advisory-tfv-2.rst37 Earlier versions of TF (prior to `commit 495f3d3`_) did not assign this bit.
58 .. _commit 495f3d3: https://github.com/ARM-software/arm-trusted-firmware/commit/495f3d3
Dsecurity-advisory-tfv-8.rst40 (referring to the version of the code as of `commit c385955`_):
84 line 19 (referring to the version of the code as of `commit c385955`_):
101 .. _commit c385955: https://github.com/ARM-software/arm-trusted-firmware/commit/c385955
Dsecurity-advisory-tfv-4.rst34 The macro code is at line 52, referring to the version of the code as of `commit
121 .. _commit c396b73: https://github.com/ARM-software/arm-trusted-firmware/commit/c396b73
Dsecurity-advisory-tfv-1.rst12 | Versions | v1.2 and v1.3 (since commit `48bfb88`_) |
161 .. _48bfb88: https://github.com/ARM-software/arm-trusted-firmware/commit/48bfb88
/trusted-firmware-a-3.4.0/docs/getting_started/
Dprerequisites.rst83 CI for feedback on commit message conformance.
155 …curl -Lo $(git rev-parse --git-dir)/hooks/commit-msg https://review.trustedfirmware.org/tools/hook…
156 chmod +x $(git rev-parse --git-dir)/hooks/commit-msg
Dbuild-options.rst133 build to be uniquely identified. Defaults to the current git commit id.
/trusted-firmware-a-3.4.0/docs/plat/
Drcar-gen3.rst119 commit 552754a6ee82bab25d1bdf28c8261a4518e65e4d
130 commit 80105192cba9e704ebe8df7ab84095edc2922f84
140 commit 4cdeda511f8037015b568396e6dcc3d8fb41e8c0
147 commit 7876320f88802b22d4e2daf7eb027dd14175a0f8
Drz-g2.rst110 | commit 72ca39737f974db44723760623d1b29980c00a88
119 | commit 46ce9e777c1314ccb78906992b94001194eaa87b
126 | commit f8394f232b1eab649ce2df5c5f15b0e528c92091
/trusted-firmware-a-3.4.0/
DMakefile1423 for commit in `git rev-list --no-merges $$COMMON_COMMIT..HEAD`; \
1425 printf "\n[*] Checking style of '$$commit'\n\n"; \
1426 git log --format=email "$$commit~..$$commit" \
1429 git diff --format=email "$$commit~..$$commit" \
/trusted-firmware-a-3.4.0/docs/design_documents/
Dmeasured_boot_poc.rst34 since commit cf56848.
/trusted-firmware-a-3.4.0/docs/components/
Dsecure-partition-manager-mm.rst181 For an example of all the changes in context, you may refer to commit
/trusted-firmware-a-3.4.0/docs/
Dchange-log.md107 …- initial commit for attestation service ([d174083](https://review.trustedfirmware.org/plugins/git…