I posted a large patch that ports babl-0.0.22 to all 30 of the architectures I have access to, but it is currently stuck in the moderation queue. Is there someone/where else I can send it instead, or can I trust that it will be made visible to this list by the moderator in good time?

Cheers, Gary

Hi Martin,

On Mon, Feb 23, 2009 at 05:36:31PM +0100, Martin Nordholts wrote:

Gary V. Vaughan wrote:

I posted a large patch that ports babl-0.0.22 to all 30 of the architectures I have access to, but it is currently stuck in the moderation queue. Is there someone/where else I can send it instead, or can I trust that it will be made visible to this list by the moderator in good time?

Cheers, Gary

Hi

That is so nice that I would accept any of the following: 1. A mail directly to me with the patch attached 2. A link to gegl.pastebin.com with your patch 3. Create a bug report and attach the patch there (under the babl component):
http://bugzilla.gnome.org/browse.cgi?product=GEGL

The last one is preferable but if you don't feel like registering for whatever reason feel free to do 1 or 2 and I'll take care of the rest

Many thanks! I'm pretty sure we already have a gnome bugzilla account, so when I find the login details I'll also paste my babl patch into a new report.

I am close to a similarly monstrous patch to port gegl itself to those same 30 architectures, which I'll add to bugzilla later this week.

Cheers, Gary

On Tue, Feb 24, 2009 at 07:23:04AM +0100, Martin Nordholts wrote:

I am close to a similarly monstrous patch to port gegl itself to those same 30 architectures, which I'll add to bugzilla later this week.

Cheers, Gary

Is it possible for you to work against SVN trunk of babl and GEGL? That way your patches will apply cleanly which makes things slightly easier for us

Yes, I think that should be possible. How stable is the trunk, compared to 0.0.22 releases? It might make more sense for us to track HEAD while we shepherd the patches we need into the upstream tree if the API is the same, and a release is likely in the next few months.

Do you have up to date git mirrors of the current trunks, since the patch merging in git is far easier to use?

Cheers, Gary