Gimp Traffic #40 For 2 May 2001

By Cris Flagg

The GIMP Homepage (http://www.gimp.org) | The GIMP News Archive (http://www.xach.com/gimp/news/index.html) | The GIMP Mailing Lists (http://www.gimp.org/mailing_list.html) | The GIMP FAQ (http://www.rru.com/~meo/gimp/)

Table Of Contents

• Standard Format
• Text Format
• XML Source
• Mailing List Stats For This Week
• Threads Covered

  1.	13 Apr 2001	(8 posts)	How To Avoid Creating New Colors in the Gimp
  2.	21 Apr 2001 - 23 Apr 2001	(7 posts)	Submitting Bugs to Bugzilla
  3.	25 Apr 2001 - 26 Apr 2001	(8 posts)	Bugs and Bugzilla

Mailing List Stats For This Week

We looked at 25 posts in 81K.

There were 12 different contributors. 5 posted more than once. 4 posted last week too.

The top posters of the week were:

• 5 posts in 17K by Sven Neumann <sven@gimp.org>
• 5 posts in 13K by egger@suse.de
• 4 posts in 17K by Raphael Quinet <quinet@gamers.org>
• 2 posts in 7K by David Kirkby <drkirkby@ntlworld.com>
• 2 posts in 5K by Michael Natterer <mitch@gimp.org>
• Full Stats

1. How To Avoid Creating New Colors in the Gimp

13 Apr 2001 (8 posts) Archive Link: "Can I avoid Gimp creating new coulours ???"

People: Blue Lang, Sven Neumann, Sven Neumann , Kelly Martin, 

David Kirkby was writing a scientific application that required bitmaps of specific colors to be read as data. The interpolation of colors was causing problems with the application, and David wondered if there was any way to turn off interpolation. Kelly Martin suggested using indexed mode, and Blue Lang suggested " "dialogs-$gt;pallete edit->new" then choose only the colors you want and image->mode->index(ed) the image to 4 colors, and you should be rocking. "

David added that the images needed to be in 24 bit mode for the software. Sven Neumann suggested disabling anti-aliasing and changing the Interpolation type to Nearest-Neighbor in the Preferences Dialog. He also added " If you use the EllipseSelect tool and fill the selection, disable antialiasing in the EllipseSelect tool options. If you are stroking the selection, use the Pencil to stroke. "

2. Submitting Bugs to Bugzilla

21 Apr 2001 - 23 Apr 2001 (7 posts) Archive Link: "Bugs 52383 and 52385"

People: Danniel Egger, Raphael Quinet, Federico Mena Quintero, , Sven Neumann, Daniel Egger

Mike Kelly submitted two bug reports to Bugzilla a few weeks ago and they have remained "UNCONFIRMED" Mike wanted to know if this was the right thing to do with bug reports and if there was anything he could do to help. Sven Neumann said that writing to the mailing list was a to get people to notice a bug. The one major flaw with the list, as he saw it, was that it didn't send mail to the bugs-list. Daniel Egger thanked Mike for following through on the bug and added that the developers following Bugzilla were busy and hadn't been confirming many bugs lately. He added " Creating proper bugreports is a very good start, having a fix in hand is even better but fixing foreign bugs will make you a god.... :) " Raphael Quinet added " I wish that more people would use the bug database for reporting bugs. This is the correct way to do it. And these bug reports included all the necessary information to reproduce and analyze the bugs, which is very nice." Raphael also suggested making the old gimp bugs list the default owner for all Gimp bugs. This would e-mail any update to the list until someone took ownership of the bug. Federico Mena Quintero added " Go to the module administration page in Bugzilla. You can enter a list of addresses that will be mailed when a new bug is logged for a module."

Raphael Quinet had some additional comments about committing a bug fix to CVS after it has been reported to Bugzilla. " I have a small suggestion for the handling of bug reports and bug fixes: Whenever you commit a bug fix in CVS and this bug was reported in bugzilla, do the following things:

• In the commit message (and Changelog entry), include a reference to the bug number. For example: "Added a test around the while loop (fixes bug #52385)."
• After this, go to bugzilla and add a one-line comment to the bug report indicating in which branch the bug was fixed. For example: "fixed in CVS HEAD" or "fixed in gimp_1_2 branch". You can also mark the bug as closed/fixed while you are adding the comment.

3. Bugs and Bugzilla

25 Apr 2001 - 26 Apr 2001 (8 posts) Archive Link: "Help needed with unconfirmed gimp bugs (especially for Windows)"

People: , Sven Neumann, Raphael Quinet, Daniel Egger

Raphael Quinet has been helping confirm bugs on Solaris and Unix, but is unable to confirm bugs for Windows, IRIX, HP-UX or other OSes. These bugs usually stay unconfirmed for quite a while. Raphael want to know if there were people on the development list that would also be interested in actively confirming bugs on these and other platforms.

Sven Neumann asked if anyone had changed Bugzilla so that it would email bug reports to the bugs-list. After various permissions and accounts dealings, Daniel Egger and Raphael changed all open bugs to belong to the bugs-list. Raphael warned of the oncoming spam to the bugs-list of 250+ changed bug reports.

Sharon And Joy