Eli: are you saying that those commits were not included in the testing bundles? If so, why do we need to re-run the release tests? (Or is there something else?)
Robby On Mon, Aug 2, 2010 at 2:12 PM, Eli Barzilay <e...@barzilay.org> wrote: > On Aug 2, Jay McCarthy wrote: >> On Mon, Aug 2, 2010 at 4:31 AM, Eli Barzilay <e...@barzilay.org> wrote: >> > On Aug 2, Matthias Felleisen wrote: >> >> On Aug 2, 2010, at 6:11 AM, Eli Barzilay wrote: >> >> >> >> > And for the (near) future -- figure out what's happenning in the >> >> > teaching languages. I get the impression that things are moving >> >> > there almost randomly. >> >> >> >> No, this isn't random; it is unsynchronized: >> > >> > (Yeah, I used "random" in a random sense...) >> > >> >> -- Shriram asked Jay to add define-datatype >> > >> > (and hashes? was there more?) >> >> define-datatype, match, hashes >> >> These are the commits: >> >> http://github.com/plt/racket/commit/407dcee206678785b4b87bb513d7ba5f55ad8ab5 >> >> http://github.com/plt/racket/commit/eeada45868d73c02b59f5c1ecd16e414d5a114ac >> >> http://github.com/plt/racket/commit/9eb053d4db1efd2881e1f749ad6b1eb12a6e8152 > > (For future references, the sha1 is all that is needed.) > > None of these commits are included. This leaves the last mess: > running proper tests. > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life! > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev