Home
last modified time | relevance | path

Searched full:patches (Results 1 – 25 of 50) sorted by relevance

12

/qemu/docs/devel/
H A Dtrivial-patches.rst1 .. _trivial-patches:
3 Trivial Patches
9 Trivial patches that change just a few lines of code sometimes languish
11 review. This is often the case for patches that do not fall under an
14 The trivial patches team take on the task of reviewing and building pull
15 requests for patches that:
18 - Are single patches or short series (max 2-4 patches).
30 …git://github.com/vivier/qemu.git trivial-patches - `browse <https://github.com/vivier/qemu/tree/tr…
35 The trivial patches team rotates the duty of collecting trivial patches
38 1. Identify trivial patches on the development mailing list.
[all …]
H A Dsubmitting-a-patch.rst7 the documentation. However, we get a lot of patches, and so we have
15 .. list-table:: Minimal Checklist for Patches
21 * - Patches contain Signed-off-by: Your Name <author@email>
47 Writing your Patches
66 Base patches against current git master
74 It is also okay to base patches on top of other on-going work that is
83 Split up long patches
86 Split up longer patches into a patch series of logical code changes.
96 good candidate for splitting into multiple patches. For more thoughts on
97 properly splitting patches and writing good commit messages, see `this
[all …]
H A Dstable-process.rst22 Generally, the following patches are considered stable material:
24 * Patches that fix severe issues, like fixes for CVEs
26 * Patches that fix regressions
47 patches that are stable candidates are tracked by the maintainers.
67 a git branch with a release candidate and send the patches out to
68 ``qemu-devel@nongnu.org`` for review. If any of your patches are included,
71 nominate other patches that you think are suitable for inclusion. After
H A Dsubmitting-a-pull-request.rst17 **Resend the patches with the pull request** as emails which are
35 people have reviewed the patches you're putting in the pull request,
36 make sure you've copied their signoffs across. (If you use the `patches
37 tool <https://github.com/stefanha/patches>`__ to add patches from email
39 you're updating patches manually or in some other way you'll need to
43 request says these patches are ready to go into QEMU now, so they must
H A Dmaintainers.rst11 - reviewing patches and suggesting changes
12 - collecting patches and preparing pull requests
29 patches that touch their area of code.
69 spontaneous feedback. This will ensure that patches touching a given
H A Dindex-process.rst6 Notes about how to interact with the community and how and where to submit patches.
16 trivial-patches
/qemu/scripts/codeconverter/codeconverter/
H A Dpatching.py234 def apply_patches(s: str, patches: Iterable[Patch]) -> str:
235 """Apply a sequence of patches to string
243 """Patches are sorted by byte position,
244 patches at the same byte position are applied in the order
250 for i,p in sorted(enumerate(patches), key=patch_sort_key):
310 self.patches: List[Patch] = []
345 self.patches.clear()
363 DBG("Generating patches for %r", m)
368 self.patches.append(p)
385 """Replace self.original_content after applying patches from self.patches"""
[all …]
H A Dtest_patching.py39 f.patches.append(p2.append('XXX'))
41 # apply all patches:
/qemu/
H A DREADME.rst67 Submitting patches
76 When submitting patches, one common approach is to use 'git
78 qemu-devel@nongnu.org mailing list. All patches submitted must contain
79 a 'Signed-off-by' line from the author. Patches should follow the
84 Additional information on submitting patches can be found online via
H A D.patchew.yml156 # HEAD pointing to a commit that has the patches applied on top of "base"
185 # HEAD pointing to a commit that has the patches applied on top of "base"
214 # HEAD pointing to a commit that has the patches applied on top of "base"
239 # HEAD pointing to a commit that has the patches applied on top of "base"
H A D.b4-config2 # Common b4 settings that can be used to send patches to QEMU upstream.
/qemu/scripts/
H A Dgit.orderfile2 # order file for git, to produce patches which are easier to review
29 # semantic patches
/qemu/subprojects/
H A Ditertools-0.11-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dbilge-0.2-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Deither-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dsyn-2-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dquote-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dunicode-ident-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dbilge-impl-0.2-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Darbitrary-int-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dproc-macro2-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dproc-macro-error-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
H A Dproc-macro-error-attr-1-rs.wrap9 # bump this version number on every change to meson.build or the patches:
/qemu/tests/qemu-iotests/
H A DREADME17 * Feedback and patches
/qemu/.github/workflows/
H A Dlockdown.yml26 functionality). However, we get a lot of patches, and so we have some

12