all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kkebreau@posteo.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 02/02: gnu: python-pillow: Update to 4.3.0.
Date: Mon, 25 Dec 2017 12:09:23 -0500	[thread overview]
Message-ID: <87fu7ywx8c.fsf@posteo.net> (raw)
In-Reply-To: <87k1xawye9.fsf@posteo.net> (Kei Kebreau's message of "Mon, 25 Dec 2017 11:44:14 -0500")

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

Kei Kebreau <kkebreau@posteo.net> writes:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Sun, Dec 24, 2017 at 06:16:29PM -0500, Kei Kebreau wrote:
>>> I've attempted to use the upstream patch, but it involves some GIT
>>> binaries which aren't supported by GNU patch. Among other hackish
>>> options, temporarily upgrading to the appropriate upstream commit may
>>> fix this for now.
>>
>> Does it work if you pass '--binary' to patch-flags?
>
> It does not. Maybe I could use 'diff --binary' to patch the files into
> existence?

Using 'diff --text' on the non-text files seems to work. The patch file
is encoded as 'raw-text' according to Emacs. Please take a look at our
bug #29849.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-12-25 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171222165126.23934.71746@vcs0.savannah.gnu.org>
     [not found] ` <20171222165127.9F00B2044A@vcs0.savannah.gnu.org>
2017-12-24 17:57   ` 02/02: gnu: python-pillow: Update to 4.3.0 Mark H Weaver
2017-12-24 17:59   ` Mark H Weaver
2017-12-24 19:08     ` Kei Kebreau
2017-12-24 21:57       ` Mark H Weaver
2017-12-24 23:16         ` Kei Kebreau
2017-12-25  0:03           ` Leo Famulari
2017-12-25 16:44             ` Kei Kebreau
2017-12-25 17:09               ` Kei Kebreau [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=87fu7ywx8c.fsf@posteo.net \
    --to=kkebreau@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.