Re: [Chicken-hackers] pending patches

[Felix]

From: Peter Bex <address@hidden>
Subject: Re: [Chicken-hackers] pending patches
Date: Mon, 12 Mar 2012 10:13:29 +0100

> On Mon, Mar 12, 2012 at 08:25:45AM +0100, Felix wrote:
>> Hi!
>> 
>> Too many patches are floating in limbo in the moment (and I'm aware of
>> being unable to catch up, particularly in the case of the more involved
>> patches which I really like to review before they go into "master").
> 
> There are no really involved ones left anymore, I think.
> 
>> A suggestion: if a patch remains pending for a longer period, it might
>> be sensible to create a trac ticket, add the patch and assign the
>> ticket to someone (when in doubt, assign it to me). Otherwise patches
>> will get lost, or submitters will feel ignored.
> 
> What works great for me is using the "flag" feature of mutt.  When a
> message comes in, it start out being "unread".  When I read it and see
> it's a patch, I flag it.  Then when someone applies the patch, I
> unflag it.  So everything that requires attention is either unread or
> flagged.
> 
> That way I can easily see which patches are still outstanding.  These
> are, in chronological order:
> 
> - [PATCH] fix special cases for vector/list-ref in scrutinizer when argument 
> count is wrong
>    (here there's a reply with a modified patch)

Hm. Can't find that one.

> - [CR] deprecate "make" syntax in setup-api
>    (you said you'd send a patch to the list for this one)

Did so just now.

> - Re: [Chicken-hackers] [PATCH] random returns the same number on x86_64 all 
> the time
>    (this is a reply to a patch mail which was applied, but the reply
>     contains another patch)

I lost track.

> - [PATCH] Raise error on construction of too large vectors/blobs
>    (this is a long thread with multiple patches)

I have to review this, since it seems to duplicate ##sys#check-range.

> - [PATCH] Bugfix for #791 and unpack flonums correctly for integer?

Can't remember.

> - [PATCH] Allow assert to accept an arbitrary expression as the message

Ah, yeah.

> - [PATCH] Fix a few more mistakes in types.db

Can't remember.


What a mess.


cheers,
felix