Re: open issue review (easy stuff)

2004-03-03 Thread Robert Spier
... and then I got bored. ;) Thanks, all those changes applied. -R

Re: open issue review (easy stuff)

2004-03-03 Thread Will Coleda
Here's some more. 27305 - just applied by Leo today. (but not closed! bad leo, no donut! =-) 27303 - spam 27308 - applied, with a note that the applier didn't have perms to close it. 27336 - mine, patch applied by chromatic, needs closing. 25948 - fix committed by leo. willowBored now!/willow

Re: open issue review (easy stuff)

2004-03-03 Thread Robert Spier
willowBored now!/willow /me runs and hides. Applied! (I should just give you access.) -R On Wednesday, March 3, 2004, at 06:39 PM, Robert Spier wrote: ... and then I got bored. ;) Thanks, all those changes applied. -R -- Will Coke Coleda

Re: open issue review (easy stuff)

2004-03-02 Thread Will Coleda
On Tuesday, January 20, 2004, at 06:03 PM, Robert Spier wrote: If you respond to this message, with the ticket id and brief reason why it can be closed, i.e. patch applied, patch rejected, bad idea.. I'll do the labor of updating the ticketing system. -R 18044: Assembler doesn't return a useful

Re: open issue review (easy stuff)

2004-01-23 Thread Dan Sugalski
At 12:56 PM -0800 1/22/04, Robert Spier wrote: Is there any way to get RT to close tickets (or change their status) entirely via e-mail? That'd make this a lot easier if we could throw a: RT-Status: Closed or something like it in the reply to a bug report that notes the bug has been fixed.

Re: open issue review (easy stuff)

2004-01-23 Thread Robert Spier
Right, good point. In that case, if we could give our intrepid and possibly slightly mad volunteers Dave Pippenger (dpippen) and Stephane Peiry (stephane) privs on the bug and todo queue for parrot, that'd be great -- we can start handing out todo tickets to folks for doing. done-o. -R

Re: open issue review (easy stuff)

2004-01-22 Thread Robert Spier
Is there any way to get RT to close tickets (or change their status) entirely via e-mail? That'd make this a lot easier if we could throw a: RT-Status: Closed or something like it in the reply to a bug report that notes the bug has been fixed. I could implement this, but there are

Re: open issue review (easy stuff)

2004-01-21 Thread Arvindh Rajesh Tamilmani
Robert Spier wrote: 24941: [PATCH] RE: More Buffer IO Bugs (was: Strangeness when printing to file) patch applied. Arvindh __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus

open issue review (easy stuff)

2004-01-20 Thread Robert Spier
Here are 177 currently outstanding parrot issues in the RT system. You can see more detail on them by going to: http://rt.perl.org/ clicking on guest access, and then typing the number into the upper right hand corner box. what we're mostly looking for are issues that can already be marked

Re: open issue review (easy stuff)

2004-01-20 Thread Matt Fowles
Robert~ Thanks for taking this on. Matt 22558: Another Hack at constant propogation Aplied or Fixed and then applied (I forget which) 24847: [patch] simplify register stacks (remove code duplication) Reject (resubmitted late as a different patch which was applied)

Re: open issue review (easy stuff)

2004-01-20 Thread Robert Spier
Thanks for taking this on. No problemo. 22558: Another Hack at constant propogation Aplied or Fixed and then applied (I forget which) 24847: [patch] simplify register stacks (remove code duplication) Reject (resubmitted late as a different patch which was applied) Noted. (FYI, for the

Re: open issue review (easy stuff)

2004-01-20 Thread Simon Glover
Here are a few that can be closed; I'm sure this is far from a complete list. Simon 15357: Read write ops in core.ops are broken Close - the broken ops no longer exist. 16114: [PATCH] faster assembler Close - we don't use assemble.pl any more. 17974: make clean removes