On Wed, 2009-11-18 at 00:23 -0200, Nelson A. de Oliveira wrote:
--- app/core/gimpimage-convert.c.old 2009-11-18 00:18:55.0 -0200
+++ app/core/gimpimage-convert.c 2009-11-18 00:19:34.0 -0200
@@ -835,8 +835,6 @@
/* Convert to indexed? Build histogram if necessary. */
Hi!
On Wed, Nov 18, 2009 at 4:23 AM, Martin Nordholts ense...@gmail.com wrote:
Please generate the patch as a commit according to these instructions:
http://gimp.org/bugs/howtos/submit-patch.html
Patch available at
http://people.debian.org/~naoliv/misc/0001-Fix-memleaks-in-plug-ins.patch
A
--
Christopher Howard
http://indicium.us
http://theologia.indicium.us
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Cox wrote:
On Oct 20, 2009, at 1:39 PM, Sven Neumann wrote:
Hi,
On Tue, 2009-10-20 at 12:22 -0800, Christopher Howard wrote:
Though having a far
Christopher Howard wrote:
Jay Cox wrote:
On Oct 20, 2009, at 1:39 PM, Sven Neumann wrote:
Hi,
On Tue, 2009-10-20 at 12:22 -0800, Christopher Howard wrote:
Though having a far from sufficient understanding of how the GIMP brush
painting process works, it seems to me like this is the
Hi again!
I gave another look on the possible mem leaks and created another patch:
http://people.debian.org/~naoliv/misc/0001-Fix-memory-leakages.patch
Can somebody review them, please?
There is both
http://people.debian.org/~naoliv/misc/0001-Fix-memleaks-in-plug-ins.patch
On Thu, Nov 19, 2009 at 11:17 AM, James Cox jay...@gimp.org wrote:
Christopher Howard wrote:
Thinking about this some more, the error diffusion is probably not even
necessary. You should be able to get by with some random dithering like
the following (if it wasn't slower than molasses):
