Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
> If you would like to see any of these ideas
> implemented, or you have some of your own - please
> respond to this on the list.
I've amother one. Parrot has some internal settings and tweakable magic
constants, mainly all inside the garbage collector. I
On Wed, 3 Nov 2004 12:52:26 -0800 (PST), Joshua Gatcomb
<[EMAIL PROTECTED]> wrote:
[snip]
> What we would like to do is determine if what we have
> done so far is sufficient or, if not, what specifically
> people would like to see. Some of our unimplemented
> ideas so far are:
> 1. Include the co
At 5:25 PM -0500 11/3/04, Matt Diephouse wrote:
On Wed, 3 Nov 2004 16:04:38 -0500, Matt Fowles <[EMAIL PROTECTED]> wrote:
I think it would be really cool if commits that had a significant
increase or descrease in speed would be flagged. Possibly just a
section of the page could be a table with
On Wed, 3 Nov 2004 16:04:38 -0500, Matt Fowles <[EMAIL PROTECTED]> wrote:
> I think it would be really cool if commits that had a significant
> increase or descrease in speed would be flagged. Possibly just a
> section of the page could be a table with commit dates and the percent
> effect they ha
All~
I think it would be really cool if commits that had a significant
increase or descrease in speed would be flagged. Possibly just a
section of the page could be a table with commit dates and the percent
effect they had. This table would not contain all commits dates, but
only the most recent
All:
Matt Diephouse and I spent the majority of our time
coming up with a flexible design and gathering
historical statistics. We didn't spend a lot of time
in how to present the data since everybody has their
own opinion (including us).
What we would like to do is determine if what we have
done
