summaryrefslogtreecommitdiff
path: root/graphics/gimp1/files/patch-am (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Retire print/gimp-print, graphics/gimp1, and graphics/gimp-pmosaicMichael Johnson2007-09-161-19/+0
| | | | Notes: svn path=/head/; revision=199568
* Upgrade to 1.2.1.Vanilla I. Shu2001-01-241-1/+0
| | | | Notes: svn path=/head/; revision=37513
* Update to version 1.1.22. From the information I have, vanilla might notJim Mock2000-05-191-6/+6
| | | | | | | | have a vacation for a while, so I figured I wouldn't let this get stale if that's the case. Notes: svn path=/head/; revision=28613
* Merge the gimp1 and gimp1-i18n ports, and update to GIMP 1.1.17.Jeremy Lea2000-02-241-12/+13
| | | | | | | | PR: ports/16837, ports/16913 Reviewed by: maintainers Notes: svn path=/head/; revision=26246
* Upgrade to 1.0.1.Vanilla I. Shu1998-09-301-3/+3
| | | | Notes: svn path=/head/; revision=13559
* Add patches to call fpsetmask(0) at startup time, for gimp itselfJohn Polstra1998-05-191-0/+19
and for the plug-ins. Linux defaults to this (I think), but FreeBSD does not. Thus SIGFPEs happen at inopportune times under FreeBSD. GIMP catches the signals, but prompts at the standard input asking what to do about them. On my system, I start GIMP from a window manager menu, and this prompt to standard input caused the window manager and every child of it to enter the STOPPED state. Not nice at all. Why the other processes got stopped too, I don't understand. Notes: svn path=/head/; revision=11056
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-01 10:22:14 +0000