search for: patch2

...follows: Thanks. I've tried some of this, and am a little confused. > > 1) Add the upstream repo as another remote: > > git remote add upstream https://github.com/the/original/repo > > 2) Pull the upstream master with a different name: > > git pull upstream master:patch2 I've done all that, and now on my local copy I have a branch. I called it "upstreamMaster", because at this point it matches the upstream master, and I intend to maintain it that way. > > 3) Edit, add, commit and push patch2 to your fork: > > git checkout patch2 &gt...

...e you can pull the original master branch and call it whatever you want in one command. The process is as follows: 1) Add the upstream repo as another remote: git remote add upstream https://github.com/the/original/repo 2) Pull the upstream master with a different name: git pull upstream master:patch2 3) Edit, add, commit and push patch2 to your fork: git checkout patch2 ... git push origin patch2 4) open a fresh new PR from "patch2" (the first one is intact). I?aki > > Duncan Murdoch >

Solaris 7 doesn't have a ut_host element in utmp...patch let's bsd-login.c compile with this knowledge: *** openssh-1.2pre13.orig/bsd-login.c Fri Nov 19 00:32:34 1999 --- openssh-1.2pre13/bsd-login.c Fri Nov 19 14:23:49 1999 *************** *** 40,45 **** --- 40,46 ---- static char *rcsid = "$Id: bsd-login.c,v 1.1 1999/11/19 04:32:34 damien Exp $"; #endif /*

There is a problem with the patch I sent out yesterday. The patches for the glm code are applied in the wrong place. I have removed the patch file and will have a real one available latter today. Ross =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help",

...tried some of this, and am a little confused. > > >> 1) Add the upstream repo as another remote: >> >> git remote add upstream https://github.com/the/original/repo >> >> 2) Pull the upstream master with a different name: >> >> git pull upstream master:patch2 >> > > I've done all that, and now on my local copy I have a branch. I called it > "upstreamMaster", because at this point it matches the upstream master, and > I intend to maintain it that way. > > >> 3) Edit, add, commit and push patch2 to your fork: &...

On 25/01/2018 2:57 AM, I?aki ?car wrote: > For what it's worth, this is my workflow: > > 1. Get a fork. > 2. From the master branch, create a new branch called fix-[something]. > 3. Put together the stuff there, commit, push and open a PR. > 4. Checkout master and repeat from 2 to submit another patch. > > Sometimes, I forget the step of creating the new branch and I

...ed the src.rpm from http://mirrors.kernel.org/opensuse/distribution/SL-OSS-factory/inst-source/suse/src/ruby-1.8.4-9.src.rpm Then I installed it with "rpm -i ruby-1.8.4-9.src.rpm" Then I went to /usr/src/packages/SPECS and made the below edits # diff ruby.spec.orig ruby.spec 28d27 < Patch2: ruby-1.8.4-no-eaccess.diff 181d179 < %patch2 I then compiled up the rpm via "rpmbuild -bb ruby.spec" I then went to the /usr/src/packages/RPMS/i586 directory and installed the all the various 1.8.4 rpms. HTH Greg -- Greg Freemyer The Norcross Group Forensics for the 21st C...

patch is self explanatory, I trust. im not sure about patch2, (I didnt do a controlled test). -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch URL: <http://www.zytor.com/pipermail/syslinux/attachments/20050528/b3266150/attachment.ksh> -------------- next part -------------- An embedded and ch...

...st have pointer type.") in llvm::StroreInst::init and llvm::LoadInst::init functions This is requared including llvm/Type.h or moving init function definitions to iMemory.cpp. I don't known more acceptable variant and then sending as attachment both versions: iMemory.patch1 and iMemory.patch2 . Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: iMemory.patch2 Type: application/octet-stream Size: 2072 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040701/3dba11c4/attachment.obj> -------------- next p...

hello all, (cc'ing some other package maintainers) I attached a patch against vorbis-tools-1.1.1 to make the code also compile against the upcoming FLAC 1.1.3, beta available here: http://prdownloads.sourceforge.net/flac/flac-1.1.3-beta2.tar.gz?download changelog: http://flac.cvs.sourceforge.net/*checkout*/flac/flac/doc/html/changelog.html with FLAC 1.1.3 there is no need for EasyFLAC. the

...(int, const char *, const char *, mode_t); int rmdir(const char *); -<!alpha,ia64,mips,mips64,sparc,sparc64> int pipe(int *); +<!alpha,ia64,mips,mips64,sh,sparc,sparc64> int pipe(int *); mode_t umask(mode_t); int chroot(const char *); int symlink(const char *, const char *); only in patch2: unchanged: --- a/usr/klibc/arch/sh/syscall.S +++ b/usr/klibc/arch/sh/syscall.S @@ -5,7 +5,7 @@ * r4..r7 contain arguments 0-3 per the standard calling convention, * and arguments 4-5 are passed in r0 and r1. * - * The return value is in r3 rather than standard r0. + * The return value is in...

I have some questions in terms of how to use puppet of configuration management for software patches. My previous approach was it to create a puppet module for each patch ... Like Patch1 includes (FileA, FileB, FileC), Patch2 includes (FileD, FileE)... So far so good and that works but now i have to create a Patch3 with lets say FileF and FileA included. As you can see there will be a puppet conflict as i can''t deploy the same files within different modules. What is the right architecture and method to mana...

http://bugs.freedesktop.org/show_bug.cgi?id=23212 Summary: oops on rmmod nouveau with nv31m Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...n/icecast2 -c /etc/icecast/icecast.xml <p>Regards, -- ricardo "I just stopped using Windows and now you tell me to use Mirrors?" - said Aunt Tillie, just before downloading 2.5.3 kernel. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch2.diff Type: text/x-diff Size: 12878 bytes Desc: patch2.diff Url : http://lists.xiph.org/pipermail/icecast-dev/attachments/20020223/88dc822d/patch2.bin

...e, I assumed the answer was "no", so I downloaded the SRPMs of less for both C6 and C7, and did a comparison. I found that it was easy to fix the C6 less to use the correct POSIX regex engine as follows: 1. Copy less-394-search.patch from the C7 SRPM, and add it back into less.spec as Patch2. 2. Remove the line "BuildRequires: pcre-devel". 3. Remove "--with-regex=pcre" from the %configure line in less.spec. 4. Change the release number. I changed 13 to 13posix, so that the resultant RPMS have names like less-436-13posix.el6 instead of less-436-13.el6 5. Rebui...

...ill teach llvm-mca how to use method > `resolveVariantSchedClass()` to resolve variant classes. llvm-mca will generate an error if the variant scheduling class cannot be resolved. > > Review https://reviews.llvm.org/D46697 <https://reviews.llvm.org/D46697> is the union of patch1 and patch2 only. > It is not meant to be reviewed at this stage, since it contains the code > changes related to patch1. > > The third patch is available here: https://reviews.llvm.org/D46698 <https://reviews.llvm.org/D46698>. > D46698 requires patch1 and patch2. > > Bonus (option...

...ncorporated in dovecot-final? I use rpmbuild to create new rpms from the latest tarball but in that process still several patches are included during the build. I wonder if they are still needed in rc15. I use the orignal spec file (the latest I could find) was created for rc7 and in there I see: Patch2 dovecot-0.99.10-mbox-patch Seems to be to change the order of ./Mail before ./mail Patch3 dovecot-CVE-2006-2414 Overview from CVE db:Directory traversal vulnerability in Dovecot 1.0 beta and 1.0 allows remote attackers to list files and directories under the mbox parent directory and obtain mailbo...

...------ An embedded and charset-unspecified text was scrubbed... Name: dovecot-patch1.diff URL: <http://dovecot.org/pipermail/dovecot/attachments/20100901/207bdd8c/attachment-0006.pl> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dovecot-patch2.diff URL: <http://dovecot.org/pipermail/dovecot/attachments/20100901/207bdd8c/attachment-0007.pl> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dovecot-patch3.diff URL: <http://dovecot.org/pipermail/dovecot/attachments/20100901/207bd...

...eVariantSchedClass(). The last patch of the sequence will teach llvm-mca how to use method `resolveVariantSchedClass()` to resolve variant classes. llvm-mca will generate an error if the variant scheduling class cannot be resolved. Review https://reviews.llvm.org/D46697 is the union of patch1 and patch2 only. It is not meant to be reviewed at this stage, since it contains the code changes related to patch1. The third patch is available here: https://reviews.llvm.org/D46698. D46698 requires patch1 and patch2. Bonus (optional) patches: 1) [X86] Teach scheduling models how to recognize zero-idioms...

...-3.2.1/debian/patches/series xen-3-3.2.1/debian/patches/series --- xen-3-3.2.1/debian/patches/series +++ xen-3-3.2.1/debian/patches/series @@ -18,0 +19,3 @@ +xen-3.2.CVE-2008-2004.1.hg80730d294e51.diff +xen-3.2.CVE-2008-2004.2.hg5824167feb81.diff +xen-3.2.CVE-2008-2004.3.hg0016f5a1dd5a.diff only in patch2: unchanged: --- xen-3-3.2.1.orig/debian/patches/xen-3.2.CVE-2008-2004.1.hg80730d294e51.diff +++ xen-3-3.2.1/debian/patches/xen-3.2.CVE-2008-2004.1.hg80730d294e51.diff @@ -0,0 +1,128 @@ + +# HG changeset patch +# User Keir Fraser <keir.fraser at citrix.com> +# Date 1210688387 -3600 +# Node ID...