From: Dominic Hopf <dmaphy@googlemail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Nick Cross <nick@goots.org>, lilydjwg <lilydjwg@gmail.com>,
zsh-users@zsh.org
Subject: Re: It seems that I find a zle -F full CPU bug
Date: Thu, 17 Jul 2014 20:30:07 +0200 [thread overview]
Message-ID: <CAOTt9Uzyx8f-uvw=0TOvx+==zn0d4MByEw1=GPYT7JzmH2w77Q@mail.gmail.com> (raw)
In-Reply-To: <140717101819.ZM3771@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
That did it, thanks very much for your support. Fedora Updates are on their
way… :-)
2014-07-17 19:18 GMT+02:00 Bart Schaefer <schaefer@brasslantern.com>:
> On Jul 17, 5:52pm, Dominic Hopf wrote:
> }
> }
> } I've tried applying the patch for the Fedora but unfortunately the build
> } fails with attached output. Basically, I just did a
> }
> } git diff -u 79abe00e1d73b3f0681343a70e3e7f84e5e3d647
> } 7e04c1a53ddada7a848753d151e18f9469788b98 -- Doc/Zsh/zle.yo
> } Src/Zle/zle_main.c >| ~/rpmbuild/SOURCES/0001-zsh-fix-cpuload-issue.patch
> }
> } to create the patch I'm applying in the SPEC file. Is this something I
> have
> } done wrong?
>
> Your "git diff" is covering too much ground, you've pulled in multiple
> unrelated patches but only gotten the subset of the deltas that apply
> to zle_main.c, so interdependent changes are lost and breakage results.
>
> Try (backslash-newlines inserted for readability):
>
> git diff -u 73db206838e427348cb91f1955692da5d2820d00 \
> 7e04c1a53ddada7a848753d151e18f9469788b98 -- \
> Doc/Zsh/zle.yo Src/Zle/zle_main.c \
> >| ~/rpmbuild/SOURCES/0001-zsh-fix-cpuload-issue.patch
>
--
Diese E-Mail ist nicht mit GPG signiert, da ich sie vom Webinterface aus
geschrieben habe.
This mail is not signed with GPG because I wrote it from web interface.
prev parent reply other threads:[~2014-07-17 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 5:04 lilydjwg
2014-02-20 7:30 ` Bart Schaefer
2014-02-20 9:40 ` Peter Stephenson
2014-02-20 13:16 ` lilydjwg
2014-07-16 13:55 ` Nick Cross
2014-07-16 16:01 ` Bart Schaefer
2014-07-16 17:10 ` Nick Cross
2014-07-16 17:50 ` Bart Schaefer
2014-07-17 13:52 ` Nick Cross
2014-07-17 15:52 ` Dominic Hopf
2014-07-17 17:18 ` Bart Schaefer
2014-07-17 18:30 ` Dominic Hopf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOTt9Uzyx8f-uvw=0TOvx+==zn0d4MByEw1=GPYT7JzmH2w77Q@mail.gmail.com' \
--to=dmaphy@googlemail.com \
--cc=lilydjwg@gmail.com \
--cc=nick@goots.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).