Search results
Create the page "Patch" on this wiki! See also the search results found.
- * [[patch]]735 bytes (83 words) - 19:25, 29 January 2012
- ...lex-dev<BR>bison<BR>gawk<BR>sed<BR>grep<BR>autoconf<BR>automake<BR>make<BR>patch<BR>diffstat<BR>diffutils<BR>libstdc++-dev<BR>libtool<BR>libtool-dev<BR>libl4 KB (501 words) - 12:33, 20 August 2012
- ...rces-c_2.8.0.bb xerces-c]||[http://patchwork.openembedded.org/patch/20133/ patch sent] but for OE-Core; changes requested224 KB (27,125 words) - 20:57, 16 July 2013
- if patch had standard cv, could write automated tools to parse12 KB (1,803 words) - 17:38, 12 August 2020
- ...a git hook (or similar) that will email the security list when a security patch is committed to the project(s), using the standard CVE format.4 KB (536 words) - 17:39, 12 August 2020
- ####Patch submissions (all OE components)5 KB (741 words) - 17:43, 12 August 2020
- * 'Patch accepted' notifications to contributors (Ruslan)3 KB (422 words) - 17:39, 12 August 2020
- # Patch submission process (gitlab) or any other technology.3 KB (503 words) - 17:40, 12 August 2020
- ...https://git.openembedded.org/, and there is no change to the OpenEmbedded patch review process.1 KB (214 words) - 10:52, 25 November 2019
- * [[How to submit a patch to OpenEmbedded]]946 bytes (124 words) - 13:36, 5 May 2022
- ...e a recipe for a given source tree and set up an environment where you can patch the source easily (which you often need to do when you're writing a recipe)10 KB (1,629 words) - 20:45, 23 February 2023
- ...ttps://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html#patch-upstream-status Recipe Style Guide]''400 bytes (53 words) - 08:28, 16 April 2024