Enable installing git by default on Windows.

Enable installing git by default on Windows.

BUG=79356
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107206

[M-A Ruel, 2011-10-22 01:29:14]

lgtm

[commit-bot: I haz the power, 2011-10-24 21:06:05]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/cmp@chromium.org/8369019/1

[commit-bot: I haz the power, 2011-10-24 21:06:06]

Can't apply patch for file depot_tools/bootstrap/win/win_tools.bat.
While running patch -p0 --forward --force;
patching file depot_tools/bootstrap/win/win_tools.bat
Hunk #1 FAILED at 25.
1 out of 1 hunk FAILED -- saving rejects to file
depot_tools/bootstrap/win/win_tools.bat.rej

[commit-bot: I haz the power, 2011-10-24 22:06:17]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/cmp@chromium.org/8369019/5001

[commit-bot: I haz the power, 2011-10-24 22:06:18]

Can't apply patch for file depot_tools/bootstrap/win/win_tools.bat.
While running patch -p0 --forward --force;
patching file depot_tools/bootstrap/win/win_tools.bat
Hunk #1 FAILED at 25.
1 out of 1 hunk FAILED -- saving rejects to file
depot_tools/bootstrap/win/win_tools.bat.rej

[M-A Ruel, 2011-10-24 22:31:46]

CRLF, just commit manually...
Le 24 oct. 2011 18:06, <commit-bot@chromium.org> a écrit :

> Can't apply patch for file depot_tools/bootstrap/win/win_**tools.bat.
> While running patch -p0 --forward --force;
> patching file depot_tools/bootstrap/win/win_**tools.bat
> Hunk #1 FAILED at 25.
> 1 out of 1 hunk FAILED -- saving rejects to file
> depot_tools/bootstrap/win/win_**tools.bat.rej
>
>
>
http://codereview.chromium.**org/8369019/<http://codereview.chromium.org/8369...
>

[cmp, 2011-10-25 21:11:30]

Testing:

1. without WIN_TOOLS_FORCE and no git.bat -> Git is installed
2. without WIN_TOOLS_FORCE and git.bat -> Git is not installed
3. with WIN_TOOLS_FORCE=1 and no git.bat -> Git is installed
4. with WIN_TOOLS_FORCE=1 and git.bat -> Git is installed

First 3 work fine, fourth doesn't.  WIN_TOOLS_FORCE is only checked if the batch
file is missing and then only causes the tool to be installed again if the
--version check fails for some reason.  So I'm going to assume the test results
look good, too, and land this locally.