git-fetch: fix --keep vs --thin
When --keep is specified there is no reason to pass --thin to git-fetch-pack, which are mutually exclusive. This does not hurt because fetch-pack disables thin transfer when both are given internally, but still is confusing. Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
parent
b9718d41c7
commit
482faa8daf
@ -20,6 +20,7 @@ verbose=
|
|||||||
update_head_ok=
|
update_head_ok=
|
||||||
exec=
|
exec=
|
||||||
upload_pack=
|
upload_pack=
|
||||||
|
keep=--thin
|
||||||
while case "$#" in 0) break ;; esac
|
while case "$#" in 0) break ;; esac
|
||||||
do
|
do
|
||||||
case "$1" in
|
case "$1" in
|
||||||
@ -347,7 +348,7 @@ fetch_main () {
|
|||||||
( : subshell because we muck with IFS
|
( : subshell because we muck with IFS
|
||||||
IFS=" $LF"
|
IFS=" $LF"
|
||||||
(
|
(
|
||||||
git-fetch-pack $exec $keep --thin "$remote" $rref || echo failed "$remote"
|
git-fetch-pack $exec $keep "$remote" $rref || echo failed "$remote"
|
||||||
) |
|
) |
|
||||||
while read sha1 remote_name
|
while read sha1 remote_name
|
||||||
do
|
do
|
||||||
|
Loading…
Reference in New Issue
Block a user