See microsoft/git#306.

See microsoft/git#306.

See microsoft/git#306.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.

This check verifies that the ODB matches what we supplied, but there are
some subtleties around Windows path names that can cause inexact matches
to be logically the same. Since this check is really intended only for
debugging and development purposes, let's remove it for now as a quick
workaround.

This was originally part of #304, as I hit it more often in that effort. However,
this was hit during the Scalar release process, so I'll need to generate new
installers.