[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