From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: do_patch and binary patches
Date: Mon, 23 Sep 2013 15:24:40 +0100 [thread overview]
Message-ID: <1578169.W0gr9jI3si@helios> (raw)
In-Reply-To: <CALbNGRROB7mqTpQr=K-HUotmQx2RhCJ-Cnf=BsmSj_W6svWj6Q@mail.gmail.com>
Hi Andreas,
On Wednesday 04 September 2013 13:44:32 Andreas Müller wrote:
> did not find any helpful hint - and cannot remember somebody asked
> already: Is there a specific reason why our do_patch ignores binary
> files - or is there a way to allow binary files in patches?
I don't have any specific knowledge about this limitation, and I see you've
worked around it in the mean time; but maybe this is because quilt doesn't
(didn't?) support patching binary files. You could try setting PATCHTOOL =
"patch" instead.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-09-23 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 11:44 do_patch and binary patches Andreas Müller
2013-09-23 14:24 ` Paul Eggleton [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=1578169.W0gr9jI3si@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox