[racket-dev] "~e" vs "~.s"

When I tried to do that to look thru your changes to the framework, I
was overwhelmed with all the reindentation that you did. Is there a
way to avoid seeing that?

Robby

On Wed, Aug 25, 2010 at 8:53 PM, Eli Barzilay <eli at barzilay.org> wrote:
> On Aug 25, Eli Barzilay wrote:
>> [...]  If I touched your code, it would be a good idea to check that
>> I did the right thing.
>
> A git tip, to make this easier: you don't need to look throughout the
> diff of the whole push -- that has too many changes in many cases
> (including this).  To conveniently see just one commit, you can use
> `git show' with the commit's id:
>
>  git show 606b7f6
>
> Even that would be too verbose to sift through, but git can filter
> only a subset of the tree.  For example:
>
>  git show 606b7f6 -- collects/drracket
>
> or filter on several using using shell tricks:
>
>  git show 606b7f6 -- collects/{drracket,framework}
>
> and you can also cd into the directory and run the command there with
> a `--relative' flag that will show only the changes in this directory
> (and relative to it):
>
>  cd collects/drracket; git show 606b7f6 --relative
>
> To see the files that were changed in this commit (so you can see what
> to choose for filtering):
>
>  git show --name-only 606b7f6
>
> or get the same with stats that tell you how much was changed:
>
>  git show --stat 606b7f6
>
> or to see roughly which parts of the tree a commit was touching:
>
>  git show --dirstat 606b7f6
>
> (this is rough, since it shows just directories where many changes
> happened, for example, this comman won't show you the change to
> collects/unstable since there was only one file).
>
> --
>          ((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
>