Fix lastchange.py when running on native win32 python

Fix lastchange.py when running on native win32 python

When running as runhooks, it's not run via cygwin like it was when run in the build, and isn't able to find git. I believe the test that checked for both cygwin and win32 before was incorrect (but was always run via cygwin before so didn't matter).

Additionally, when runhooks runs it, it's from above src/, so the cwd isn't in the repo. So, pass in the directory of the script itself so that git can find its repo.

BUG=112264
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=120089

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=120110

[M-A Ruel, 2012-02-01 19:23:19]

:/

lgtm

[scottmg, 2012-02-01 19:25:21]

On 2012/02/01 19:23:19, Marc-Antoine Ruel wrote:
> :/

yah :( I made quite a mess. everything's always harder than it seems.

[Peter Kasting, 2012-02-02 06:40:56]

FWIW, I'm not convinced that "running under runhooks means this is not run via
cygwin" -- I think it is more correct to say that running under runhooks means
it MAY not be run via cygwin.  Hopefully this still works in that case.

(I say this because I have a setup that forces the cygwin python first in the
PATH rather than the depot_tools python.  I think this gives Marc-Antoine
heartburn.)

[M-A Ruel, 2012-02-02 14:17:08]

On 2012/02/02 06:40:56, Peter Kasting wrote:
> FWIW, I'm not convinced that "running under runhooks means this is not run via
> cygwin" -- I think it is more correct to say that running under runhooks means
> it MAY not be run via cygwin.  Hopefully this still works in that case.


> (I say this because I have a setup that forces the cygwin python first in the
> PATH rather than the depot_tools python.  I think this gives Marc-Antoine
> heartburn.)

No, that's fine with me.

[scottmg, 2012-02-02 18:04:02]

Sorry, yes, that should have read "may not be run via cygwin". I believe
the cygwin case should still work fine.

On Wed, Feb 1, 2012 at 10:40 PM, <pkasting@chromium.org> wrote:

> FWIW, I'm not convinced that "running under runhooks means this is not run
> via
> cygwin" -- I think it is more correct to say that running under runhooks
> means
> it MAY not be run via cygwin.  Hopefully this still works in that case.
>
> (I say this because I have a setup that forces the cygwin python first in
> the
> PATH rather than the depot_tools python.  I think this gives Marc-Antoine
> heartburn.)
>
>
https://chromiumcodereview.**appspot.com/9317037/<https://chromiumcodereview....
>