From: Johannes Schindelin Date: Sun, 26 Jan 2020 09:30:12 GMT Subject: Re: [PATCH v4 4/7] remote rename/remove: handle branch..pushRemote config values Message-ID: In-Reply-To: <055e52dd-9349-697c-277f-abc9ac8ae85e@googlemail.com> Hi Bert, On Sat, 25 Jan 2020, Bert Wesarg wrote: > On 25.01.20 01:46, Johannes Schindelin wrote: > > Hi Bert, > > > > On Fri, 24 Jan 2020, Bert Wesarg wrote: > > > > > When renaming or removing a remote with > > > > > > git remote rename X Y > > > git remote remove X > > > > > > Git already renames/removes any config values from > > > > > > branch..remote = X > > > > > > to > > > > > > branch..remote = Y > > > > > > As branch..pushRemote also names a remote, it now also renames > > > or removes these config values from > > > > > > branch..pushRemote = X > > > > > > to > > > > > > branch..pushRemote = Y > > > > > > Signed-off-by: Bert Wesarg > > > > > > --- > > > > This commit seems to cause a failure in t5505: > > https://dev.azure.com/gitgitgadget/git/_build/results?buildId=27833&view=ms.vss-test-web.build-test-results-tab > > > > Here is the excerpt of the log: > > > > [...] > > > > Could you have a look to see whether the code or the test need to be > > adjusted? > > please ensure that you have v4 of this patch. What you see was a bug in v3. I was talking about the current state of what was merged into `pu`: https://github.com/gitgitgadget/git/commit/6f032056fd7534b8efd712994c02531d83ada957 (note the red X indicating the build failure). If you already fixed this, and Junio merely has to pick it up, all the better. Thanks, Dscho