author | Junio C Hamano <junkio@cox.net> | |
Thu, 24 Nov 2005 07:46:13 +0000 (23:46 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 25 Nov 2005 21:49:17 +0000 (13:49 -0800) | ||
commit | e8cc80d03934cc607e3a4d89a05350c238dbf9c5 | |
tree | 2b276b1200a1c6f3e6d50ec435530eea9308a2df | tree | snapshot |
parent | f678dd180a037283decb76201b537dca24de848f | commit | diff |
parse-remote and ls-remote clean-up.
There is no reason to use git-sh-setup from git-ls-remote.
git-parse-remote can help the caller to use .git/remotes
shortcut if it is run inside a git repository, but can still be
useful outside a git repositoryas long as the caller does not
use any shortcut. Use "git-rev-parse --git-dir" to figure out
where the GIT_DIR is, instead of using git-sh-setup.
This also makes "git-ls-remote origin" to work from inside a
subdirectory of a git managed repository as a side effect.
Signed-off-by: Junio C Hamano <junkio@cox.net>
There is no reason to use git-sh-setup from git-ls-remote.
git-parse-remote can help the caller to use .git/remotes
shortcut if it is run inside a git repository, but can still be
useful outside a git repositoryas long as the caller does not
use any shortcut. Use "git-rev-parse --git-dir" to figure out
where the GIT_DIR is, instead of using git-sh-setup.
This also makes "git-ls-remote origin" to work from inside a
subdirectory of a git managed repository as a side effect.
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-ls-remote.sh | diff | blob | history | |
git-parse-remote.sh | diff | blob | history |