Don't confuse VS 2013 with VS 2017

Don't confuse VS 2013 with VS 2017

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

BUG=683729
Review-Url: https://codereview.chromium.org/2741783006
Cr-Commit-Position: refs/heads/master@{#456226}
Committed: https://chromium.googlesource.com/chromium/src/+/fead74a8e3d55044bc89fe96500275a0b5e3f24c

[brucedawson, 2017-03-10 23:11:57]

Description was changed from

==========
Don't confuse VS 2013 with VS 2017

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

R=scottmg@chromium.org
BUG=683729
==========

to

==========
Don't confuse VS 2013 with VS 2017

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

BUG=683729
==========

[brucedawson, 2017-03-10 23:12:35]

brucedawson@chromium.org changed reviewers:
+ sebmarchand@chromium.org
- scottmg@chromium.org

[brucedawson, 2017-03-10 23:12:56]

Minor improvement to avoid version switching confusion - PTAL.

[brucedawson, 2017-03-10 23:38:13]

brucedawson@chromium.org changed reviewers:
+ thestig@chromium.org
- sebmarchand@chromium.org

[brucedawson, 2017-03-10 23:40:31]

PTAL

[Lei Zhang, 2017-03-10 23:46:00]

lgtm

[brucedawson, 2017-03-10 23:46:53]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2017-03-10 23:47:25]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-11 00:14:52]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489189613038960, "parent_rev":
"a26877dfeb89300f2da958471d2ab9f72766cf38", "commit_rev":
"fead74a8e3d55044bc89fe96500275a0b5e3f24c"}

[commit-bot: I haz the power, 2017-03-11 00:15:33]

Description was changed from

==========
Don't confuse VS 2013 with VS 2017

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

BUG=683729
==========

to

==========
Don't confuse VS 2013 with VS 2017

Building with VS 2017 using a packaged toolchain is not yet supported
but if you try to do it you get a surprising result - the VS 2013
toolchain gets downloaded. This adds a 2013 check to avoid this, and
also simplifies/corrects an existing 2017 check and comment.

This lets us fail-fast if a user tries the VS 2017 depot-tools
combination before it is supported.

BUG=683729

Review-Url: https://codereview.chromium.org/2741783006
Cr-Commit-Position: refs/heads/master@{#456226}
Committed:
https://chromium.googlesource.com/chromium/src/+/fead74a8e3d55044bc89fe965002...
==========

[commit-bot: I haz the power, 2017-03-11 00:15:35]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/fead74a8e3d55044bc89fe965002...