Re: [racket-dev] [plt] Push #21102: master branch updated

2010-09-17 Thread Robby Findler
Since you asked... probably the string-constants library should not be used for those error messages, since none of the other error messages are translated, but since they are already being used it seems fine to continue (at least to me). Robby _

Re: [racket-dev] [plt] Push #21108: master branch updated

2010-09-17 Thread Casey Klein
On Fri, Sep 17, 2010 at 11:39 AM, ro...@racket-lang.org wrote: robby has updated `master' from c6fc7137ee to ce211ac364.  http://git.racket-lang.org/plt/c6fc7137ee..ce211ac364 =[ 1 Commits ]== Directory summary:  10.1%

Re: [racket-dev] [plt] Push #21108: master branch updated

2010-09-17 Thread Robby Findler
On Fri, Sep 17, 2010 at 11:50 AM, Casey Klein clkl...@eecs.northwestern.edu wrote: On Fri, Sep 17, 2010 at 11:39 AM,  ro...@racket-lang.org wrote: robby has updated `master' from c6fc7137ee to ce211ac364.  http://git.racket-lang.org/plt/c6fc7137ee..ce211ac364 =[ 1 Commits

Re: [racket-dev] [plt] Push #21108: master branch updated

2010-09-17 Thread Casey Klein
On Fri, Sep 17, 2010 at 11:52 AM, Robby Findler ro...@eecs.northwestern.edu wrote: On Fri, Sep 17, 2010 at 11:50 AM, Casey Klein clkl...@eecs.northwestern.edu wrote: On Fri, Sep 17, 2010 at 11:39 AM,  ro...@racket-lang.org wrote: robby has updated `master' from c6fc7137ee to ce211ac364.  

Re: [racket-dev] [plt] Push #21108: master branch updated

2010-09-17 Thread Robby Findler
Sure, a parameter is fine. And since we're going to have a paramter, then defaulting to the old way seems best. Thanks! Robby On Fri, Sep 17, 2010 at 12:02 PM, Casey Klein clkl...@eecs.northwestern.edu wrote: On Fri, Sep 17, 2010 at 11:52 AM, Robby Findler ro...@eecs.northwestern.edu wrote:

[racket-dev] rename + changes = bad? (was: Fwd: [plt] Push #21110: master branch updated)

2010-09-17 Thread John Clements
Oof... it looks like doing a rename plus a few changes pretty effectively hides those changes, though I can dig them out with 'git annotate'. Do we have a policy (or should we have) a policy stating that you shouldn't put a rename and modifications to that file in the same commit? John Begin

Re: [racket-dev] rename + changes = bad? (was: Fwd: [plt] Push #21110: master branch updated)

2010-09-17 Thread Sam Tobin-Hochstadt
On Fri, Sep 17, 2010 at 1:36 PM, John Clements cleme...@brinckerhoff.org wrote: Oof... it looks like doing a rename plus a few changes pretty effectively hides those changes, though I can dig them out with 'git annotate'.  Do we have a policy (or should we have) a policy stating that you

Re: [racket-dev] rename + changes = bad? (was: Fwd: [plt] Push #21110: master branch updated)

2010-09-17 Thread John Clements
On Sep 17, 2010, at 11:03 AM, Sam Tobin-Hochstadt wrote: On Fri, Sep 17, 2010 at 1:36 PM, John Clements cleme...@brinckerhoff.org wrote: Oof... it looks like doing a rename plus a few changes pretty effectively hides those changes, though I can dig them out with 'git annotate'. Do we

Re: [racket-dev] flvector-copy

2010-09-17 Thread Matthew Flatt
I'm preparing to push this patch, but also generalizing `flvector-copy' to accept start and end positions like `vector-copy'. At Thu, 16 Sep 2010 20:46:58 -0400, Will M. Farr wrote: The attached patch against the current git master adds an flvector-copy procedure (along with docs and tests);