[debbugs-tracker] bug#17519: closed ([PATCH] take into account QuantumScale when reading imagemagick images)

[GNU bug Tracking System]

Your message dated Wed, 21 May 2014 12:54:07 -0700
with message-id <address@hidden>
and subject line Re: [PATCH] take into account QuantumScale when reading 
imagemagick images
has caused the debbugs.gnu.org bug report #17519,
regarding [PATCH] take into account QuantumScale when reading imagemagick images
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
17519: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17519
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] take into account QuantumScale when reading imagemagick images Date: Sat, 17 May 2014 15:25:56 +0200

Symptom:
On Macs with a freshly compiled "nexstep" emacs and no rsvg library, the splash 
screen displays a corrupted picture.

This patch is here corrects the "pixel pushing" (default) method for loading 
images from ImageMagick to properly interpret pixels from images loaded with 
ImageMagick compiled with any pixel quantum value. (Q32 for instance)

--

0001-whitespace-cleanup-removed-tabs.patch
Description: Binary data

0002-remove-visibility-of-some-variables.patch
Description: Binary data

0003-properly-scale-pixels-from-pixelmagick.patch
Description: Binary data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [PATCH] take into account QuantumScale when reading imagemagick images
>
>
>
>
> Date: 
>
> Wed, 21 May 2014 12:54:07 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
>
>
>
>
> Thanks for testing it.  I installed the fix as trunk bzr 117134 and am 
> marking the bug as fixed.
>
> Unfortunately this is an old bug and currently the emacs-24 branch is 
> accepting fixes only for regressions, so this bug fix is not scheduled 
> for the very next release, but it should appear in the release after 
> that.  If it's more urgent to fix it for some reason, please let us know.
>
>
> --- End Message ---