| /openbmc/qemu/docs/devel/ |
| H A D | submitting-a-pull-request.rst | 1 .. _submitting-a-pull-request:
3 Submitting a Pull Request
8 :ref:`submitting-a-patch`
10 will need to submit pull requests, although occasionally for a large
11 patch series we might ask a submitter to send a pull request. This page
12 documents our recommendations on pull requests for those people.
14 A good rule of thumb is not to send a pull request unless somebody asks
17 **Resend the patches with the pull request** as emails which are
18 threaded as follow-ups to the pull request itself. The simplest way to
19 do this is to use ``git format-patch --cover-letter`` to create the
[all …]
|
| H A D | maintainers.rst | 11 - reviewing patches and suggesting changes
12 - collecting patches and preparing pull requests
13 - tending to the long term health of their area
14 - participating in other project activities
22 --------------------
25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__
34 .. list-table:: Meaning of support status in MAINTAINERS
36 :header-rows: 1
38 * - Status
39 - Meaning
[all …]
|
| H A D | trivial-patches.rst | 1 .. _trivial-patches:
7 --------
14 The trivial patches team take on the task of reviewing and building pull
15 requests for patches that:
17 - Do not fall under an actively maintained subsystem.
18 - Are single patches or short series (max 2-4 patches).
19 - Only touch a few lines of code.
22 qemu-trivial@nongnu.org.**
25 ------------
30 - git://github.com/vivier/qemu.git trivial-patches - `browse <https://github.com/vivier/qemu/tree/t…
[all …]
|
| /openbmc/qemu/.github/workflows/ |
| H A D | lockdown.yml | 1 # Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown
10 pull-requests: write
14 runs-on: ubuntu-latest
16 - uses: dessant/repo-lockdown@v2
18 pr-comment: |
21 This repository is a read-only mirror of the project's repostories hosted
22 on https://gitlab.com/qemu-project/qemu.git.
23 The project does not process merge requests filed on GitHub.
29 lock-pr: true
30 close-pr: true
|
| /openbmc/openbmc/meta-security/ |
| H A D | README.md | 1 Master-next:
2 …//gitlab.com/akuster/meta-security/badges/master-next/pipeline.svg)](https://gitlab.com/akuster/me…
4 …tus](https://gitlab.com/akuster/meta-security/badges/master/pipeline.svg)](https://gitlab.com/akus…
6 Meta-security
9 The bbappend files for some recipes (e.g. linux-yocto) in this layer need
15 If meta-security is included, but security is not enabled as a
18 You have included the meta-security layer, but
35 URI: git://git.openembedded.org/openembedded-core
38 URI: git://git.openembedded.org/meta-openembedded/meta-oe
47 Assuming the security layer exists at the top-level of your
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/ |
| H A D | README.md | 1 meta-oe
6 URI: git://github.com/openembedded/openembedded-core.git
10 e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
14 pacman -S lib32-gcc-libs lib32-glibc
17 sudo apt-get install gcc-multilib linux-libc-dev:i386
19 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
22 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PAT…
24 You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
27 Note, it is discouraged to send patches via GitHub pull request system. Such
30 'git request-pull' to generate an email referencing your git repository.
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci.rst | 16 These tests are also used as gating tests before merging pull requests.
21 On QEMU, the gating process happens during the pull request. The approval is
22 done by the project leader running its own set of tests. The pull request gets
25 .. include:: ci-jobs.rst.inc
26 .. include:: ci-runners.rst.inc
29 ----------
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/ |
| H A D | README.md | 2 ------------
5 URI: git://git.openembedded.org/openembedded-core
8 URI: git://git.openembedded.org/meta-openembedded
11 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gnome]' in the subject'
14 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-gnome][P…
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/ |
| H A D | README.md | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
9 meta-xfce depends on meta-oe, meta-gnome and meta-multimedia in this repository.
11 To avoid dependencies on meta-multimedia you need to mask recipes by adding
14 BBMASK = "meta-xfce/recipes-multimedia"
16 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce]' in the subject'
19 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-xfce][PA…
|
| /openbmc/docs/ |
| H A D | maintainer-workflow.md | 5 for sub-project maintainers to follow before approving patches.
7 - Manually verify the contributor has signed the ICLA (individual) or is listed
9 - Executed CLAs can be found [in the CLA repository][1].
10 - If you were not added to the appropriate CLA repository ACL send an email to
12 - If a CLA for the contributor is found, accept the patch(1).
13 - If a CLA is not found, request that the contributor execute one and send it to
15 - Do not accept the patch(1) until a signed CLA (individual _or_ corporate)
17 - The CCLA form can be found at [CCLA template][2].
18 - The ICLA form can be found at [ICLA template][3].
21 forks of upstream projects, like the Linux kernel or U-Boot.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/ |
| H A D | README.md | 1 meta-initramfs
6 small-sized initramfs.
10 ------------
14 URI: git://git.openembedded.org/meta-openembedded
19 -----------
21 Send patches / pull requests to openembedded-devel@lists.openembedded.org
22 with '[meta-initramfs]' in the subject.
25 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-initramf…
31 -------
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/ |
| H A D | README.md | 3 URI: git://git.openembedded.org/openembedded-core
6 URI: git://git.openembedded.org/meta-openembedded
7 layers: meta-oe
10 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the sub…
13 git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-multimed…
15 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded t…
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/x265/x265/ |
| H A D | 0001-json11.cpp-Include-cstdint.patch | 12 Upstream-Status: Pending [https://bitbucket.org/multicoreware/x265_git/pull-requests/33]
14 Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
15 ---
19 diff --git a/dynamicHDR10/json11/json11.cpp b/dynamicHDR10/json11/json11.cpp
21 --- a/dynamicHDR10/json11/json11.cpp
23 @@ -25,6 +25,7 @@
31 --
|
| /openbmc/phosphor-misc/ |
| H A D | README.md | 1 # phosphor-misc
3 phosphor-misc is a collection of miscellaneous OpenBMC functions that doesn't
8 If you have a new function in mind to be hosted in phosphor-misc, it is usually
13 phosphor-misc patches are reviewed using the Gerrit instance at
14 <https://gerrit.openbmc-project.xyz>.
18 …(https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-server).
19 <https://github.com/openbmc/phosphor-misc> is a hosting mirror only and GitHub
20 pull requests are not monitored and will not be accepted.
24 - follow
25 …[the seven rules of a great git commit message](https://chris.beams.io/posts/git-commit/#seven-rul…
|
| /openbmc/openbmc/meta-openembedded/meta-python/ |
| H A D | README.md | 1 meta-python
5 -------------------------
10 -------------------------
12 The meta-python layer depends on:
14 URI: git://git.openembedded.org/openembedded-core
18 URI: git://git.openembedded.org/meta-openembedded
19 layers: meta-oe
23 -------------------------
25 The meta-openembedded mailinglist
26 (openembedded-devel@lists.openembedded.org) is used for questions,
[all …]
|
| /openbmc/openbmc/meta-aspeed/ |
| H A D | README.md | 10 URI: git://git.openembedded.org/openembedded-core
17 ------------
19 meta-aspeed patches are reviewed using the Gerrit instance at
23 [here](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-se…
24 https://github.com/openbmc/meta-aspeed is a hosting mirror only and GitHub
25 pull requests are not monitored and will not be accepted.
29 - meta-aspeed uses the [OE style
31 - follow [the seven rules of a great git commit
32 message](https://chris.beams.io/posts/git-commit/#seven-rules)
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/ |
| H A D | README.md | 1 meta-webserver
4 This layer provides support for building web servers, web-based
10 ------------
14 URI: git://git.openembedded.org/openembedded-core
18 For some recipes, the meta-oe layer is required:
20 URI: git://git.openembedded.org/meta-openembedded
21 subdirectory: meta-oe
27 ------
29 * recipes-httpd/ Web servers
30 * recipes-php/ PHP applications
[all …]
|
| /openbmc/openbmc/meta-openpower/ |
| H A D | README.md | 11 URI: git://git.openembedded.org/openembedded-core
16 URI: https://github.com/openbmc/meta-phosphor
20 URI: https://github.com/openbmc/meta-aspeed
29 ------------
31 meta-openpower patches are reviewed using the Gerrit instance at
35 [here](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-se…
36 https://github.com/openbmc/meta-openpower is a hosting mirror only and GitHub
37 pull requests are not monitored and will not be accepted.
41 - meta-openpower uses the [OE style
43 - follow [the seven rules of a great git commit
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | contributing.md | 11 subject with `[meta-raspberrypi]` as this is the global *Yocto* mailing
12 list and not a dedicated *meta-raspberrypi* mailing list.
23 <layer-component>: <short log/statement of what needed to be changed>
32 Signed-off-by: Your Name <yourname@youremail.com>
34 The `<layer-component>` is the layer component name that your changes affect.
42 for changes to multiple recipes would be `userland,vc-graphics,wayland`.
48 the above cases, please use `meta-raspberrypi` as the component name.
55 usage patterns often result in an Out-of-memory condition causing
58 Low-memory systems should continue to function without running into
59 memory-starvation conditions with minimal cost to systems with more
[all …]
|
| /openbmc/openbmc/meta-security/meta-hardening/ |
| H A D | README.md | 4 Meta-hardening
13 Building the meta-hardening layer
14 -------------------------------
26 harden-image-minimal
41 bitbake {qemu machine} harden-image-minimal
54 URI: git://git.openembedded.org/meta-openembedded/meta-oe
60 URI: git://git.openembedded.org/meta-openembedded
61 layers: meta-oe
65 -----------
67 Send pull requests, patches, comments or questions to yocto-patches@lists.yoctoproject.org
[all …]
|
| /openbmc/openbmc/meta-security/meta-tpm/ |
| H A D | README.md | 1 meta-tpm layer
4 The bbappend files for some recipes (e.g. linux-yocto) in this layer need
10 If meta-tpm is included, but tpm is not enabled as a
13 You have included the meta-tpm layer, but
30 URI: git://git.openembedded.org/openembedded-core
35 URI: git://git.openembedded.org/meta-openembedded/meta-oe
40 Adding the meta-tpm layer to your build
46 Assuming this layer exists at the top-level of your
48 location of the meta-tpm layer to bblayers.conf, along with any
52 /path/to/oe-core/meta \
[all …]
|
| /openbmc/openbmc/meta-ibm/ |
| H A D | README.md | 10 URI: git://git.openembedded.org/openembedded-core
15 URI: https://github.com/openbmc/meta-phosphor
19 URI: https://github.com/openbmc/meta-openpower
23 URI: https://github.com/openbmc/meta-aspeed
30 Witherspoon, or AC922, is an IBM POWER9 two-socket, 2U Accelerated Compute
32 [here](https://www.ibm.com/us-en/marketplace/power-systems-ac922).
44 bitbake obmc-phosphor-image
49 bitbake obmc-phosphor-image
50 bitbake phosphor-logging
53 bitbake obmc-phosphor-image
[all …]
|
| /openbmc/openbmc/meta-hpe/ |
| H A D | README.md | 10 The HPE DL360 Gen10 OpenBMC Proof of Concept is a two-socket, 1U general purpose server.
11 …ttps://buy.hpe.com/us/en/servers/rack-servers/proliant-dl300-servers/proliant-dl360-server/hpe-pro…
17 This boot process for the GXP ASIC begins with a binary bootblock before starting U-Boot,
30 bitbake obmc-phosphor-image
36 ------------
38 meta-hpe patches are reviewed using the Gerrit instance at
42 [here](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-se…
43 https://github.com/openbmc/meta-hpe is a hosting mirror only. GitHub
44 pull requests are not monitored and will not be accepted.
48 - meta-hpe uses the [OE style
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-requests-toolbelt/ |
| H A D | 720240501dca0b4eacc3295665d7ced8719e11d2.patch | 6 Upstream-Status: Submitted [https://github.com/requests/toolbelt/pull/356]
7 Signed-off-by: Khem Raj <raj.khem@gmail.com>
8 ---
9 .../redirect_request_for_dump_all.json | 302 +++++++++++++-----
10 tests/cassettes/simple_get_request.json | 16 +-
11 tox.ini | 11 +-
12 3 files changed, 239 insertions(+), 90 deletions(-)
14 diff --git a/tests/cassettes/redirect_request_for_dump_all.json b/tests/cassettes/redirect_request_…
16 --- a/tests/cassettes/redirect_request_for_dump_all.json
18 @@ -1,17 +1,25 @@
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Application.v1_0_1.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
31 "description": "The available OEM-specific actions for this resource.",
32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
60 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag"
63 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id"
66 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/type"
[all …]
|