Hi,
with git version 2.16.3 on mac os x, (fink installed)
I did
```
$ git remote rename origin monfork
```
Then I checked .git/config, all was fine but for
```
[branch "master"]
pushRemote = origin
remote = upstream
merge = refs/heads/master
```
Shouldn
is fix.
>
> At first, I was puzzled by this, because I expected `git remote rename` to
> be backed by the `git_config_copy_or_rename_section_in_file()` function
> (which my patch series does not touch).
I played around with this test data:
[sec "tio"]
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:
> >
&g
Rename C++ keyword in order to bring the codebase closer to being able
to be compiled with a C++ compiler.
Signed-off-by: Brandon Williams
---
builtin/remote.c | 66
1 file changed, 33 insertions(+), 33 deletions(-)
diff --git a/builtin/remote.c
Rename C++ keyword in order to bring the codebase closer to being able
to be compiled with a C++ compiler.
Signed-off-by: Brandon Williams
---
remote.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/remote.c b/remote.c
index 4e93753e1..2922dca07 100644
Rename C++ keyword in order to bring the codebase closer to being able
to be compiled with a C++ compiler.
Signed-off-by: Brandon Williams
---
builtin/remote.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/builtin/remote.c b/bu
Rename C++ keyword in order to bring the codebase closer to being able
to be compiled with a C++ compiler.
Signed-off-by: Brandon Williams
---
remote.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/remote.c b/remote.c
index 4e93753e1..6f79881f6 100644
--- a
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 f
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&quo
hed git config --global --unset remote.upstream.prune &&
+ git config --global remote.upstream.prune true &&
+ git -C four.four remote rename origin upstream
+'
+
cat >remotes_origin <
cd four.four &&
+ git config remote.upstream.prune true &&
+ git remote rename origin upstream
+ )
+'
+
cat >remotes_origin <
Hi,
If I have a remote branch origin/topic/foo, running
$ git remote rename origin renamed
seems to leave directory traces behind: .git/refs/remotes/origin/topic
I expected to see .git/refs/remotes/renamed/topic/foo but not
.git/refs/remotes/origin. Is this a glitch?
I see this with Git
12 matches
Mail list logo
