git remote rename problem with trailing \\ for remote.url config entries (on Windows)

One of our users has just reported that:

$ git remote rename origin origin2

will turn following remote entry:

[remote "origin"]
	url = c:\\repo\\
	fetch = +refs/heads/*:refs/remotes/origin/*

into following entry for which the url is skipped:

[remote "origin2"]
[remote "origin2"]
	fetch = +refs/heads/*:refs/remotes/origin2/*

I understand that this is caused by the trailing \\ and it's easy to 
fix, but 'git push' and 'git pull' work properly with such URLs and a

$ git clone c:\repo\

will even result in the problematic remote-entry. So I guess some kind 
of validation could be helpful.

Tested with git version 2.11.0.windows.1

-Marc