![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Jakub Narebski <jnareb@gmail.com> | |
| Mon, 4 Dec 2006 13:29:09 +0000 (14:29 +0100) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Mon, 4 Dec 2006 21:49:08 +0000 (13:49 -0800) | ||
| commit | b360cca0b100e14abffa4cae78521b493c783738 | |
| tree | 1ac23d3deca67efccd6fb2e9fdca3afef3ead4be | tree | snapshot |
| parent | e1147267afc0afa269884767c4045847d9a2be8a | commit | diff |
git-clone: Rename --use-immingled-remote option to --no-separate-remote
With making --use-separate-remote default when creating non-bare
clone, there was need for the flag which would turn off this behavior.
It was called --use-immingled-remote.
Immingle means to blend, to combine into one, to intermingle, but it
is a bit obscure word. I think it would be better to use simply
--no-separate-remote as the opposite to --use-separate-remote
option to git clone.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
With making --use-separate-remote default when creating non-bare
clone, there was need for the flag which would turn off this behavior.
It was called --use-immingled-remote.
Immingle means to blend, to combine into one, to intermingle, but it
is a bit obscure word. I think it would be better to use simply
--no-separate-remote as the opposite to --use-separate-remote
option to git clone.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| Documentation/git-clone.txt | diff | blob | history | |
| git-clone.sh | diff | blob | history |