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

Johannes Schindelin writes: > A quick test with my `empty-config-section` patch series shows that it > addresses this issue. A quick bisec confirms that the patch with the > online "git_config_set: make use of the config parser's event stream" is > responsible for

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

Hi, [I know, blast from the past...] On Mon, 13 Feb 2017, Junio C Hamano wrote: > Marc Strapetz writes: > > > One of our users has just reported that: > > > > $ git remote rename origin origin2 > > > > will turn following remote entry: > > > > [remote "origin"] > >

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

Marc Strapetz writes: > 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

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