Searched full:patch (Results 1 – 25 of 7108) sorted by relevance
12345678910>>...285
... diffs/perl5-5.33.2/installscripts.patch perl-cross-1.3.5/cnf/
56 .PHONY: patch57 patch: target80 define patch-file82 echo "Error: File to patch is unknown: $1"; \86 echo "Error: Patch to apply is unknown: $2"; \90 patch -N -b ${1} < ${2}; \92 echo "Warning: Patch already applied on `basename $1`"; \98 .PHONY: patch-openssl99 patch-openssl:112 define patch-xalan[all …]
11 This document is obsolete. In most cases, rather than using ``patch``15 a patch to the kernel or, more specifically, what base kernel a patch for24 What is a patch?27 A patch is a small text document containing a delta of changes between two31 To correctly apply a patch you need to know what base it was generated from32 and what new version the patch will change the source tree into. These33 should both be present in the patch file metadata or be possible to deduce37 How do I apply or revert a patch?40 You apply a patch with the ``patch`` program. The patch program reads a diff41 (or patch) file and makes the changes to the source tree described in it.[all …]
43 Describe your problem. Whether your patch is a one-line bug fix or72 The maintainer will thank you if you write your patch description in a76 Solve only one problem per patch. If your description starts to get77 long, that's a sign that you probably need to split up your patch.80 When you submit or resubmit a patch or patch series, include the81 complete patch description and justification for it. Don't just82 say that this is version N of the patch (series). Don't expect the83 subsystem maintainer to refer back to earlier patch versions or referenced84 URLs to find the patch description and put that into the patch.85 I.e., the patch (series) and its description should be self-contained.[all …]
51 summary of the results should be included with the patch.61 Patch preparation69 general rule, a patch should be based on the current mainline as found in76 on the area of your patch and what is going on elsewhere, basing a patch80 Only the most simple changes should be formatted as a single patch;86 - The patch series you post will almost certainly not be the series of94 patch. These changes can be small ("add a field to this structure") or96 conceptually small and amenable to a one-line description. Each patch101 changes in the same patch. If a single patch fixes a critical security106 - Each patch should yield a kernel which builds and runs properly; if your[all …]
3 …cf9038be62c49a6b5fe93f33b32f983649b2f4c4c31cc99bd18e1e5871c31443 ncurses-6.1-20190609-patch.sh.bz24 …56 4b0a4c6abce4543ac4fd4c3389b14825e73b7cddcbb01a687c5dd837f21a3b04 ncurses-6.1-20190615.patch.gz5 …56 b2302625ec2fa6dce79622670452e56ff6130dc02e655b52177264cfeff84c51 ncurses-6.1-20190623.patch.gz6 …56 48b004a3e5409a02a5e751f996fe487f5ce45be1fff38572f7cc8167b22179bf ncurses-6.1-20190630.patch.gz7 …56 faf849eed92161ac09782badf84a19ad6beae472e87d460905865e08a6ed46e4 ncurses-6.1-20190706.patch.gz8 …56 62d4954bf818659105aa1c21cc27cb2c133e02bdc7d3f6aa548caae2d1db7440 ncurses-6.1-20190713.patch.gz9 …56 0c1a54bd5de9c890d1fabcfa92bf5bf46f7eccc54a48051367e82bdb29636450 ncurses-6.1-20190720.patch.gz10 …56 0bbd08d3bd12686d4427c242d6a8fde2e299698039cd597303af713c5f538f17 ncurses-6.1-20190727.patch.gz11 …56 40e5f350a921dbd03e3d9ff93bc477ec4f1f65878f307c534882fba3b0b40507 ncurses-6.1-20190728.patch.gz12 …56 9648104311e209d17db9556d6efc898d5c80ed5fc80e8aa3cd08769544c839b8 ncurses-6.1-20190803.patch.gz[all …]
15 e di procedure per la pubblicazione delle patch; seguirle renderà la vita27 C'è sempre una certa resistenza nel pubblicare patch finché non sono28 veramente "pronte". Per semplici patch questo non è un problema.38 Poche persone guarderanno delle patch che si sa essere fatte a metà,43 Prima di creare patch47 l'invio delle patch alla comunità di sviluppo. Queste cose includono:57 - La vostra patch ha delle conseguenze in termini di prestazioni?60 incluso nella patch.71 Preparazione di una patch74 La preparazione delle patch per la pubblicazione può richiedere una quantità[all …]
8 Inviare patch: la guida essenziale per vedere il vostro codice nel kernel11 Una persona o un'azienda che volesse inviare una patch al kernel potrebbe15 vostre patch accettate.23 per delle patch relative alle associazioni per Device Tree leggete28 patch molto del lavoro più ripetitivo lo troverete già fatto per voi, tuttavia29 dovete preparare e documentare un certo numero di patch. Generalmente, l'uso43 sorgenti e desiderano che le patch siano preparate basandosi su di essi.55 Se dovete produrre le vostre patch a mano, usate ``diff -up`` o ``diff -uprN``56 per crearle. Git produce di base le patch in questo formato; se state59 Tutte le modifiche al kernel Linux avvengono mediate patch, come descritte[all …]
24 #include "patch.h"69 * Note that the patch might still be needed before klp_module_going() in klp_find_object_module()100 static struct klp_object *klp_find_object(struct klp_patch *patch, in klp_find_object() argument105 klp_for_each_object(patch, obj) { in klp_find_object()324 * /sys/kernel/livepatch/<patch>325 * /sys/kernel/livepatch/<patch>/enabled326 * /sys/kernel/livepatch/<patch>/transition327 * /sys/kernel/livepatch/<patch>/force328 * /sys/kernel/livepatch/<patch>/<object>329 * /sys/kernel/livepatch/<patch>/<object>/<function,sympos>[all …]
19 file://0001-qemu-Add-missing-wacom-HID-descriptor.patch \20 file://0003-qemu-Add-addition-environment-space-to-boot-loader-q.patch \21 file://0006-chardev-connect-socket-to-a-spawned-command.patch \22 file://0007-apic-fixup-fallthrough-to-PIC.patch \23 file://0010-configure-Add-pkg-config-handling-for-libgcrypt.patch \24 file://0001-qemu-Do-not-include-file-if-not-exists.patch \25 file://mmap2.patch \26 file://determinism.patch \27 file://0001-tests-meson.build-use-relative-path-to-refer-to-file.patch \28 file://0001-riscv-Set-5.4-as-minimum-kernel-version-for-riscv32.patch \[all …]
13 file://0001-libcxxabi-Find-libunwind-headers-when-LIBCXXABI_LIBU.patch \14 file://0002-compiler-rt-support-a-new-embedded-linux-target.patch \15 file://0003-compiler-rt-Simplify-cross-compilation.-Don-t-use-na.patch \16 file://0004-llvm-TargetLibraryInfo-Undefine-libc-functions-if-th.patch \17 file://0005-llvm-allow-env-override-of-exe-and-libdir-path.patch \18 file://0006-clang-driver-Check-sysroot-for-ldso-path.patch \19 file://0007-clang-Driver-tools.cpp-Add-lssp_nonshared-on-musl.patch \20 file://0008-clang-Prepend-trailing-to-sysroot.patch \21 file://0009-clang-Look-inside-the-target-sysroot-for-compiler-ru.patch \22 file://0010-clang-Define-releative-gcc-installation-dir.patch \[all …]
4 …These patches will be merged automatically in the corresponding common kernels. If the patch is al…5 in upstream Linux, post a backport of the patch that conforms to the patch requirements below.9 - When sending patches upstream, the commit message must contain a clear case for why the patch15 …coordinated with kernel-team@android.com. If you want to proceed, post a patch that conforms to the16 patch requirements below.18 # Common Kernel patch requirements23 - If the patch is not merged from an upstream branch, the subject must be tagged with the type of p…29 Additional requirements are listed below based on patch type33 - If the patch is a cherry-pick from Linux mainline with no changes at all34 - tag the patch subject with `UPSTREAM:`.[all …]
18 BUILD_PATCHES = "file://0001-force-static-build.patch \19 file://0002-Adjust-the-order-of-headers-to-fix-build-for-musl.patch"22 file://0003-kexec-elf-rel-use-our-elf.h.patch \23 file://0004-kexec-elf-exec.c-replace-with-our-err.h.patch \24 file://0005-crashdump-elf.c-work-around-for-sysconf-_SC_NPROCESS.patch \25 file://0006-kexec-syscall.h-work-around-missing-syscall-wrapper.patch \26 file://0007-kexec.c-add-guard-around-ENOTSUP.patch \27 file://0008-kexec.c-replace-mising-BLKGETSIZE64.patch \28 file://0009-vmcore-dmesg.c-work-around-missing-imaxdiv.patch \29 file://0010-fs2dt.c-work-around-missing-getline.patch \[all …]
49 # Drop patch fuzz info with header and footer to log file so51 bb.note("--- Patch fuzz start ---\n%s\n--- Patch fuzz end ---" % format(stdout))65 return "Patch Error: %s" % self.msg83 Clean out the patch set. Generally includes unapplying all88 def Import(self, patch, force): argument89 if not patch.get("file"):90 if not patch.get("remote"):91 raise PatchError("Patch file must be specified in patch import.")93 patch["file"] = bb.fetch2.localpath(patch["remote"], self.d)96 if not patch.get(param):[all …]
33 file://0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \34 file://0002-gcc-poison-system-directories.patch \35 file://0003-64-bit-multilib-hack.patch \36 file://0004-Use-the-defaults.h-in-B-instead-of-S-and-t-oe-in-B.patch \37 file://0005-cpp-honor-sysroot.patch \38 file://0006-Define-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch \39 file://0007-gcc-Fix-argument-list-too-long-error.patch \40 file://0008-libtool.patch \41 file://0009-gcc-armv4-pass-fix-v4bx-to-linker-to-support-EABI.patch \42 file://0010-Use-the-multilib-config-files-from-B-instead-of-usin.patch \[all …]
4 [[patch-policy]]9 necessary to patch the source of the software to get it cross-built within13 the builds. It supports three ways of applying patch sets: downloaded patches,15 global patch directory.21 If it is necessary to apply a patch that is available for download, then add it23 then Buildroot will assume it is a full URL and download the patch24 from this location. Otherwise, Buildroot will assume that the patch should be25 downloaded from +<packagename>_SITE+. It can be a single patch,26 or a tarball containing a patch series.39 These patch files should be named +<number>-<description>.patch+.[all …]
25 file://0004-Point-scripts-location-to-libdir.patch \26 file://0005-Only-generate-an-RPATH-entry-if-LD_RUN_PATH-is-not-e.patch \27 file://0006-don-t-let-the-distro-compiler-point-to-the-wrong-ins.patch \28 file://0007-warn-for-uses-of-system-directories-when-cross-linki.patch \29 file://0008-fix-the-incorrect-assembling-for-ppc-wait-mnemonic.patch \30 file://0009-Use-libtool-2.4.patch \31 file://0010-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch \32 file://0011-sync-with-OE-libtool-changes.patch \33 file://0012-Check-for-clang-before-checking-gcc-version.patch \34 file://0013-Avoid-as-info-race-condition.patch \[all …]
4 # usage: patch-kernel [ sourcedir [ patchdir [ stopversion ] [ -acxx ] ] ]5 # The source directory defaults to /usr/src/linux, and the patch8 # scripts/patch-kernel . ..11 # scripts/patch-kernel . .. -ac12 # Get the latest Linux kernel and patch it with the latest ac patch13 # scripts/patch-kernel . .. 2.4.915 # scripts/patch-kernel . .. 2.4.9 -ac17 # scripts/patch-kernel . .. 2.4.9 -ac1118 # Gets 2.4.9 with ac patch ac1123 # It then looks for patches for the next sublevel in the patch directory.[all …]
3 # usage: patch-kernel [ sourcedir [ patchdir [ stopversion ] [ -acxx ] ] ]4 # The source directory defaults to /usr/src/linux, and the patch7 # scripts/patch-kernel . ..10 # scripts/patch-kernel . .. -ac11 # Get the latest Linux kernel and patch it with the latest ac patch12 # scripts/patch-kernel . .. 2.4.914 # scripts/patch-kernel . .. 2.4.9 -ac16 # scripts/patch-kernel . .. 2.4.9 -ac1117 # Gets 2.4.9 with ac patch ac1122 # It then looks for patches for the next sublevel in the patch directory.[all …]
16 file://static-libsystemd-pkgconfig.patch \23 file://0002-don-t-use-glibc-specific-qsort_r.patch \24 file://0003-missing_type.h-add-__compare_fn_t-and-comparison_fn_.patch \25 file://0004-add-fallback-parse_printf_format-implementation.patch \26 file://0005-src-basic-missing.h-check-for-missing-strndupa.patch \27 file://0007-don-t-fail-if-GLOB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch \28 file://0008-add-missing-FTW_-macros-for-musl.patch \29 file://0009-fix-missing-of-__register_atfork-for-non-glibc-build.patch \30 file://0010-Use-uintmax_t-for-handling-rlim_t.patch \31 file://0011-test-sizeof.c-Disable-tests-for-missing-typedefs-in-.patch \[all …]