Date: Fri, 20 Sep 2013 08:05:42 -0700 (PDT) From: "Chris H" <bsd-lists@1command.com> To: "freebsd-stable" <freebsd-stable@freebsd.org> Cc: freebsd-ports-bugs@freebsd.org, freebsd-gnome@freebsd.org Subject: ports/gimp mostly broken - ports/182069: [PATCH] devel/py-gobject: Fix GFlags messages Message-ID: <589b492a211dae3fd9b5c7e254798a55.authenticated@ultimatedns.net>
next in thread | raw e-mail | index | archive | help
Greetings, I sent a PR for troubles I was having with ports/gimp, and other programs (ports) that depend on lang/python (Python-2.7), after an upgrade. In my quest to find a resolution to this problem, I stumbled on to this PR (patch): ports/182069: [PATCH] devel/py-gobject: Fix GFlags messages ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182069 ). Which was submitted on the 14th of this month, and appears to reconcile th(is|ese) issues. What is the "patch schedule"? In other words; when do patches that appear to be good, and have no apparent consequences, get pushed into the ports tree? Thank you for all your time, and consideration. --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?589b492a211dae3fd9b5c7e254798a55.authenticated>