2005-05-22 22:03:24 +04:00
|
|
|
#!/bin/sh
|
|
|
|
#
|
2005-12-14 01:30:31 +03:00
|
|
|
|
|
|
|
USAGE='<fetch-options> <repository> <refspec>...'
|
2005-11-24 11:12:11 +03:00
|
|
|
. git-sh-setup
|
2005-09-08 04:26:23 +04:00
|
|
|
. git-parse-remote
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
_x40='[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]'
|
|
|
|
_x40="$_x40$_x40$_x40$_x40$_x40$_x40$_x40$_x40"
|
|
|
|
|
2005-10-11 10:22:02 +04:00
|
|
|
LF='
|
|
|
|
'
|
|
|
|
IFS="$LF"
|
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
no_tags=
|
2005-09-30 01:35:15 +04:00
|
|
|
tags=
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
append=
|
2005-08-23 08:28:33 +04:00
|
|
|
force=
|
2005-11-18 19:31:55 +03:00
|
|
|
verbose=
|
2005-08-26 05:15:32 +04:00
|
|
|
update_head_ok=
|
2006-01-20 21:05:24 +03:00
|
|
|
exec=
|
2006-01-20 21:38:16 +03:00
|
|
|
upload_pack=
|
2005-08-23 08:28:33 +04:00
|
|
|
while case "$#" in 0) break ;; esac
|
|
|
|
do
|
|
|
|
case "$1" in
|
|
|
|
-a|--a|--ap|--app|--appe|--appen|--append)
|
|
|
|
append=t
|
|
|
|
;;
|
2006-01-27 05:11:06 +03:00
|
|
|
--upl|--uplo|--uploa|--upload|--upload-|--upload-p|\
|
|
|
|
--upload-pa|--upload-pac|--upload-pack)
|
2006-01-20 21:05:24 +03:00
|
|
|
shift
|
|
|
|
exec="--exec=$1"
|
2006-01-20 21:38:16 +03:00
|
|
|
upload_pack="-u $1"
|
2006-01-20 21:05:24 +03:00
|
|
|
;;
|
2005-08-23 08:28:33 +04:00
|
|
|
-f|--f|--fo|--for|--forc|--force)
|
|
|
|
force=t
|
2005-08-26 05:15:32 +04:00
|
|
|
;;
|
2005-09-30 01:35:15 +04:00
|
|
|
-t|--t|--ta|--tag|--tags)
|
|
|
|
tags=t
|
|
|
|
;;
|
2006-01-07 11:48:04 +03:00
|
|
|
-n|--n|--no|--no-|--no-t|--no-ta|--no-tag|--no-tags)
|
|
|
|
no_tags=t
|
|
|
|
;;
|
2005-08-26 05:15:32 +04:00
|
|
|
-u|--u|--up|--upd|--upda|--updat|--update|--update-|--update-h|\
|
|
|
|
--update-he|--update-hea|--update-head|--update-head-|\
|
|
|
|
--update-head-o|--update-head-ok)
|
|
|
|
update_head_ok=t
|
2005-08-23 08:28:33 +04:00
|
|
|
;;
|
2005-11-18 19:31:55 +03:00
|
|
|
-v|--verbose)
|
|
|
|
verbose=Yes
|
|
|
|
;;
|
2006-01-11 04:50:19 +03:00
|
|
|
-k|--k|--ke|--kee|--keep)
|
|
|
|
keep=--keep
|
|
|
|
;;
|
2005-12-14 01:30:31 +03:00
|
|
|
-*)
|
|
|
|
usage
|
|
|
|
;;
|
2005-08-23 08:28:33 +04:00
|
|
|
*)
|
|
|
|
break
|
|
|
|
;;
|
|
|
|
esac
|
2005-08-26 05:15:32 +04:00
|
|
|
shift
|
2005-08-23 08:28:33 +04:00
|
|
|
done
|
|
|
|
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
case "$#" in
|
|
|
|
0)
|
2005-08-20 14:00:03 +04:00
|
|
|
test -f "$GIT_DIR/branches/origin" ||
|
|
|
|
test -f "$GIT_DIR/remotes/origin" ||
|
2005-08-26 05:15:32 +04:00
|
|
|
die "Where do you want to fetch from today?"
|
2005-08-20 14:00:03 +04:00
|
|
|
set origin ;;
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
esac
|
2005-08-23 08:28:33 +04:00
|
|
|
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
remote_nick="$1"
|
|
|
|
remote=$(get_remote_url "$@")
|
|
|
|
refs=
|
|
|
|
rref=
|
|
|
|
rsync_slurped_objects=
|
|
|
|
|
|
|
|
if test "" = "$append"
|
|
|
|
then
|
2005-10-05 20:58:10 +04:00
|
|
|
: >"$GIT_DIR/FETCH_HEAD"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
fi
|
|
|
|
|
|
|
|
append_fetch_head () {
|
|
|
|
head_="$1"
|
|
|
|
remote_="$2"
|
|
|
|
remote_name_="$3"
|
|
|
|
remote_nick_="$4"
|
|
|
|
local_name_="$5"
|
2005-09-26 09:54:23 +04:00
|
|
|
case "$6" in
|
|
|
|
t) not_for_merge_='not-for-merge' ;;
|
|
|
|
'') not_for_merge_= ;;
|
|
|
|
esac
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
|
2005-09-02 13:34:13 +04:00
|
|
|
# remote-nick is the URL given on the command line (or a shorthand)
|
|
|
|
# remote-name is the $GIT_DIR relative refs/ path we computed
|
|
|
|
# for this refspec.
|
|
|
|
case "$remote_name_" in
|
|
|
|
HEAD)
|
|
|
|
note_= ;;
|
|
|
|
refs/heads/*)
|
|
|
|
note_="$(expr "$remote_name_" : 'refs/heads/\(.*\)')"
|
2005-09-22 00:59:54 +04:00
|
|
|
note_="branch '$note_' of " ;;
|
2005-09-02 13:34:13 +04:00
|
|
|
refs/tags/*)
|
|
|
|
note_="$(expr "$remote_name_" : 'refs/tags/\(.*\)')"
|
2005-09-22 00:59:54 +04:00
|
|
|
note_="tag '$note_' of " ;;
|
2005-09-02 13:34:13 +04:00
|
|
|
*)
|
2005-09-22 00:59:54 +04:00
|
|
|
note_="$remote_name of " ;;
|
2005-09-02 13:34:13 +04:00
|
|
|
esac
|
2005-09-22 00:59:54 +04:00
|
|
|
remote_1_=$(expr "$remote_" : '\(.*\)\.git/*$') &&
|
|
|
|
remote_="$remote_1_"
|
|
|
|
note_="$note_$remote_"
|
2005-09-02 13:34:13 +04:00
|
|
|
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
# 2.6.11-tree tag would not be happy to be fed to resolve.
|
|
|
|
if git-cat-file commit "$head_" >/dev/null 2>&1
|
|
|
|
then
|
2005-08-25 09:46:07 +04:00
|
|
|
headc_=$(git-rev-parse --verify "$head_^0") || exit
|
2005-10-05 20:58:10 +04:00
|
|
|
echo "$headc_ $not_for_merge_ $note_" >>"$GIT_DIR/FETCH_HEAD"
|
2005-11-18 19:31:55 +03:00
|
|
|
[ "$verbose" ] && echo >&2 "* committish: $head_"
|
|
|
|
[ "$verbose" ] && echo >&2 " $note_"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
else
|
2005-10-05 20:58:10 +04:00
|
|
|
echo "$head_ not-for-merge $note_" >>"$GIT_DIR/FETCH_HEAD"
|
2005-11-18 19:31:55 +03:00
|
|
|
[ "$verbose" ] && echo >&2 "* non-commit: $head_"
|
|
|
|
[ "$verbose" ] && echo >&2 " $note_"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
fi
|
|
|
|
if test "$local_name_" != ""
|
|
|
|
then
|
|
|
|
# We are storing the head locally. Make sure that it is
|
|
|
|
# a fast forward (aka "reverse push").
|
2005-09-02 13:34:13 +04:00
|
|
|
fast_forward_local "$local_name_" "$head_" "$note_"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
fast_forward_local () {
|
2005-09-10 21:40:47 +04:00
|
|
|
mkdir -p "$(dirname "$GIT_DIR/$1")"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
case "$1" in
|
|
|
|
refs/tags/*)
|
|
|
|
# Tags need not be pointing at commits so there
|
|
|
|
# is no way to guarantee "fast-forward" anyway.
|
2005-08-23 08:28:33 +04:00
|
|
|
if test -f "$GIT_DIR/$1"
|
|
|
|
then
|
2005-10-19 05:42:14 +04:00
|
|
|
if now_=$(cat "$GIT_DIR/$1") && test "$now_" = "$2"
|
|
|
|
then
|
2005-11-18 19:31:55 +03:00
|
|
|
[ "$verbose" ] && echo >&2 "* $1: same as $3"
|
2005-10-19 05:42:14 +04:00
|
|
|
else
|
|
|
|
echo >&2 "* $1: updating with $3"
|
|
|
|
fi
|
2005-08-23 08:28:33 +04:00
|
|
|
else
|
2005-09-02 13:34:13 +04:00
|
|
|
echo >&2 "* $1: storing $3"
|
2005-08-23 08:28:33 +04:00
|
|
|
fi
|
2005-09-28 05:14:27 +04:00
|
|
|
git-update-ref "$1" "$2"
|
|
|
|
;;
|
2005-08-23 08:28:33 +04:00
|
|
|
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
refs/heads/*)
|
2005-09-28 05:14:27 +04:00
|
|
|
# $1 is the ref being updated.
|
|
|
|
# $2 is the new value for the ref.
|
|
|
|
local=$(git-rev-parse --verify "$1^0" 2>/dev/null)
|
|
|
|
if test "$local"
|
2005-08-12 13:08:29 +04:00
|
|
|
then
|
2005-09-28 05:14:27 +04:00
|
|
|
# Require fast-forward.
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
mb=$(git-merge-base "$local" "$2") &&
|
|
|
|
case "$2,$mb" in
|
|
|
|
$local,*)
|
2005-09-02 13:34:13 +04:00
|
|
|
echo >&2 "* $1: same as $3"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
;;
|
|
|
|
*,$local)
|
2005-09-02 13:34:13 +04:00
|
|
|
echo >&2 "* $1: fast forward to $3"
|
2006-02-25 14:20:13 +03:00
|
|
|
echo >&2 " from $local to $2"
|
2005-09-28 05:14:27 +04:00
|
|
|
git-update-ref "$1" "$2" "$local"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
;;
|
|
|
|
*)
|
|
|
|
false
|
|
|
|
;;
|
|
|
|
esac || {
|
2005-09-02 13:34:13 +04:00
|
|
|
echo >&2 "* $1: does not fast forward to $3;"
|
2005-09-28 05:14:27 +04:00
|
|
|
case ",$force,$single_force," in
|
|
|
|
*,t,*)
|
2005-09-02 13:34:13 +04:00
|
|
|
echo >&2 " forcing update."
|
2005-09-28 05:14:27 +04:00
|
|
|
git-update-ref "$1" "$2" "$local"
|
2005-08-23 08:28:33 +04:00
|
|
|
;;
|
|
|
|
*)
|
2005-09-28 05:14:27 +04:00
|
|
|
echo >&2 " not updating."
|
2005-08-23 08:28:33 +04:00
|
|
|
;;
|
|
|
|
esac
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
}
|
|
|
|
else
|
2005-09-28 05:14:27 +04:00
|
|
|
echo >&2 "* $1: storing $3"
|
|
|
|
git-update-ref "$1" "$2"
|
2005-08-12 13:08:29 +04:00
|
|
|
fi
|
2005-07-05 22:38:37 +04:00
|
|
|
;;
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
esac
|
|
|
|
}
|
|
|
|
|
2005-08-26 05:15:32 +04:00
|
|
|
case "$update_head_ok" in
|
|
|
|
'')
|
2005-09-28 05:14:27 +04:00
|
|
|
orig_head=$(git-rev-parse --verify HEAD 2>/dev/null)
|
2005-08-26 05:15:32 +04:00
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
2005-09-30 01:35:15 +04:00
|
|
|
# If --tags (and later --heads or --all) is specified, then we are
|
|
|
|
# not talking about defaults stored in Pull: line of remotes or
|
|
|
|
# branches file, and just fetch those and refspecs explicitly given.
|
|
|
|
# Otherwise we do what we always did.
|
|
|
|
|
|
|
|
reflist=$(get_remote_refs_for_fetch "$@")
|
|
|
|
if test "$tags"
|
|
|
|
then
|
2006-01-06 06:42:12 +03:00
|
|
|
taglist=$(IFS=" " &&
|
2006-01-20 21:38:16 +03:00
|
|
|
git-ls-remote $upload_pack --tags "$remote" |
|
2006-01-06 06:42:12 +03:00
|
|
|
while read sha1 name
|
|
|
|
do
|
|
|
|
case "$name" in
|
|
|
|
(*^*) continue ;;
|
|
|
|
esac
|
|
|
|
if git-check-ref-format "$name"
|
|
|
|
then
|
|
|
|
echo ".${name}:${name}"
|
|
|
|
else
|
|
|
|
echo >&2 "warning: tag ${name} ignored"
|
|
|
|
fi
|
|
|
|
done)
|
2005-09-30 01:35:15 +04:00
|
|
|
if test "$#" -gt 1
|
|
|
|
then
|
|
|
|
# remote URL plus explicit refspecs; we need to merge them.
|
2005-10-11 10:22:02 +04:00
|
|
|
reflist="$reflist$LF$taglist"
|
2005-09-30 01:35:15 +04:00
|
|
|
else
|
|
|
|
# No explicit refspecs; fetch tags only.
|
|
|
|
reflist=$taglist
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
fetch_main () {
|
|
|
|
reflist="$1"
|
|
|
|
refs=
|
2005-07-16 11:16:24 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
for ref in $reflist
|
|
|
|
do
|
|
|
|
refs="$refs$LF$ref"
|
2005-07-16 11:16:24 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
# These are relative path from $GIT_DIR, typically starting at refs/
|
|
|
|
# but may be HEAD
|
|
|
|
if expr "$ref" : '\.' >/dev/null
|
|
|
|
then
|
|
|
|
not_for_merge=t
|
|
|
|
ref=$(expr "$ref" : '\.\(.*\)')
|
|
|
|
else
|
|
|
|
not_for_merge=
|
|
|
|
fi
|
|
|
|
if expr "$ref" : '\+' >/dev/null
|
|
|
|
then
|
|
|
|
single_force=t
|
|
|
|
ref=$(expr "$ref" : '\+\(.*\)')
|
|
|
|
else
|
|
|
|
single_force=
|
|
|
|
fi
|
|
|
|
remote_name=$(expr "$ref" : '\([^:]*\):')
|
|
|
|
local_name=$(expr "$ref" : '[^:]*:\(.*\)')
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
rref="$rref$LF$remote_name"
|
2005-09-17 22:56:41 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
# There are transports that can fetch only one head at a time...
|
|
|
|
case "$remote" in
|
|
|
|
http://* | https://*)
|
|
|
|
if [ -n "$GIT_SSL_NO_VERIFY" ]; then
|
|
|
|
curl_extra_args="-k"
|
|
|
|
fi
|
|
|
|
remote_name_quoted=$(perl -e '
|
|
|
|
my $u = $ARGV[0];
|
|
|
|
$u =~ s{([^-a-zA-Z0-9/.])}{sprintf"%%%02x",ord($1)}eg;
|
|
|
|
print "$u";
|
|
|
|
' "$remote_name")
|
|
|
|
head=$(curl -nsfL $curl_extra_args "$remote/$remote_name_quoted") &&
|
|
|
|
expr "$head" : "$_x40\$" >/dev/null ||
|
|
|
|
die "Failed to fetch $remote_name from $remote"
|
|
|
|
echo >&2 Fetching "$remote_name from $remote" using http
|
|
|
|
git-http-fetch -v -a "$head" "$remote/" || exit
|
|
|
|
;;
|
|
|
|
rsync://*)
|
|
|
|
TMP_HEAD="$GIT_DIR/TMP_HEAD"
|
|
|
|
rsync -L -q "$remote/$remote_name" "$TMP_HEAD" || exit 1
|
|
|
|
head=$(git-rev-parse --verify TMP_HEAD)
|
|
|
|
rm -f "$TMP_HEAD"
|
|
|
|
test "$rsync_slurped_objects" || {
|
|
|
|
rsync -av --ignore-existing --exclude info \
|
|
|
|
"$remote/objects/" "$GIT_OBJECT_DIRECTORY/" || exit
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
# Look at objects/info/alternates for rsync -- http will
|
|
|
|
# support it natively and git native ones will do it on
|
|
|
|
# the remote end. Not having that file is not a crime.
|
|
|
|
rsync -q "$remote/objects/info/alternates" \
|
|
|
|
"$GIT_DIR/TMP_ALT" 2>/dev/null ||
|
|
|
|
rm -f "$GIT_DIR/TMP_ALT"
|
|
|
|
if test -f "$GIT_DIR/TMP_ALT"
|
|
|
|
then
|
|
|
|
resolve_alternates "$remote" <"$GIT_DIR/TMP_ALT" |
|
|
|
|
while read alt
|
|
|
|
do
|
|
|
|
case "$alt" in 'bad alternate: '*) die "$alt";; esac
|
|
|
|
echo >&2 "Getting alternate: $alt"
|
|
|
|
rsync -av --ignore-existing --exclude info \
|
|
|
|
"$alt" "$GIT_OBJECT_DIRECTORY/" || exit
|
|
|
|
done
|
|
|
|
rm -f "$GIT_DIR/TMP_ALT"
|
|
|
|
fi
|
|
|
|
rsync_slurped_objects=t
|
|
|
|
}
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
# We will do git native transport with just one call later.
|
|
|
|
continue ;;
|
|
|
|
esac
|
2005-07-16 11:16:24 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
append_fetch_head "$head" "$remote" \
|
|
|
|
"$remote_name" "$remote_nick" "$local_name" "$not_for_merge"
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
|
2006-01-07 11:48:04 +03:00
|
|
|
done
|
|
|
|
|
|
|
|
case "$remote" in
|
|
|
|
http://* | https://* | rsync://* )
|
|
|
|
;; # we are already done.
|
|
|
|
*)
|
|
|
|
( : subshell because we muck with IFS
|
|
|
|
IFS=" $LF"
|
|
|
|
(
|
2006-02-20 11:38:39 +03:00
|
|
|
git-fetch-pack $exec $keep --thin "$remote" $rref || echo failed "$remote"
|
2006-01-07 11:48:04 +03:00
|
|
|
) |
|
|
|
|
while read sha1 remote_name
|
|
|
|
do
|
|
|
|
case "$sha1" in
|
|
|
|
failed)
|
|
|
|
echo >&2 "Fetch failure: $remote"
|
|
|
|
exit 1 ;;
|
|
|
|
esac
|
|
|
|
found=
|
|
|
|
single_force=
|
|
|
|
for ref in $refs
|
|
|
|
do
|
|
|
|
case "$ref" in
|
|
|
|
+$remote_name:*)
|
|
|
|
single_force=t
|
|
|
|
not_for_merge=
|
|
|
|
found="$ref"
|
|
|
|
break ;;
|
|
|
|
.+$remote_name:*)
|
|
|
|
single_force=t
|
|
|
|
not_for_merge=t
|
|
|
|
found="$ref"
|
|
|
|
break ;;
|
|
|
|
.$remote_name:*)
|
|
|
|
not_for_merge=t
|
|
|
|
found="$ref"
|
|
|
|
break ;;
|
|
|
|
$remote_name:*)
|
|
|
|
not_for_merge=
|
|
|
|
found="$ref"
|
|
|
|
break ;;
|
|
|
|
esac
|
|
|
|
done
|
|
|
|
local_name=$(expr "$found" : '[^:]*:\(.*\)')
|
|
|
|
append_fetch_head "$sha1" "$remote" \
|
|
|
|
"$remote_name" "$remote_nick" "$local_name" "$not_for_merge"
|
|
|
|
done
|
|
|
|
) || exit ;;
|
|
|
|
esac
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
fetch_main "$reflist"
|
|
|
|
|
|
|
|
# automated tag following
|
|
|
|
case "$no_tags$tags" in
|
|
|
|
'')
|
2006-02-23 00:10:37 +03:00
|
|
|
case "$reflist" in
|
|
|
|
*:refs/*)
|
|
|
|
# effective only when we are following remote branch
|
|
|
|
# using local tracking branch.
|
|
|
|
taglist=$(IFS=" " &&
|
|
|
|
git-ls-remote $upload_pack --tags "$remote" |
|
|
|
|
sed -ne 's|^\([0-9a-f]*\)[ ]\(refs/tags/.*\)^{}$|\1 \2|p' |
|
|
|
|
while read sha1 name
|
|
|
|
do
|
|
|
|
test -f "$GIT_DIR/$name" && continue
|
|
|
|
git-check-ref-format "$name" || {
|
|
|
|
echo >&2 "warning: tag ${name} ignored"
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
git-cat-file -t "$sha1" >/dev/null 2>&1 || continue
|
|
|
|
echo >&2 "Auto-following $name"
|
|
|
|
echo ".${name}:${name}"
|
|
|
|
done)
|
|
|
|
esac
|
2006-01-07 11:48:04 +03:00
|
|
|
case "$taglist" in
|
|
|
|
'') ;;
|
|
|
|
?*)
|
|
|
|
fetch_main "$taglist" ;;
|
|
|
|
esac
|
[PATCH] Multi-head fetch.
Traditionally, fetch takes these forms:
$ git fetch <remote>
$ git fetch <remote> <head>
$ git fetch <remote> tag <tag>
This patch updates it to take
$ git fetch <remote> <refspec>...
where:
- A <refspec> of form "<src>:<dst>" is to fetch the objects
needed for the remote ref that matches <src>, and if <dst>
is not empty, store it as a local <dst>.
- "tag" followed by <next> is just an old way of saying
"refs/tags/<next>:refs/tags/<next>"; this mimics the
current behaviour of the third form above and means "fetch
that tag and store it under the same name".
- A single token <refspec> without colon is a shorthand for
"<refspec>:" That is, "fetch that ref but do not store
anywhere".
- when there is no <refspec> specified
- if <remote> is the name of a file under $GIT_DIR/remotes/
(i.e. a new-style shorthand), then it is the same as giving
the <refspec>s listed on Pull: line in that file.
- if <remote> is the name of a file under $GIT_DIR/branches/
(i.e. an old-style shorthand, without trailing path), then it
is the same as giving a single <refspec>
"<remote-name>:refs/heads/<remote>" on the command line, where
<remote-name> is the remote branch name (defaults to HEAD, but
can be overridden by .git/branches/<remote> file having the
URL fragment notation). That is, "fetch that branch head and
store it in refs/heads/<remote>".
- otherwise, it is the same as giving a single <refspec>
that is "HEAD:".
The SHA1 object names of fetched refs are stored in FETCH_HEAD,
one name per line, with a comment to describe where it came from.
This is later used by "git resolve" and "git octopus".
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-20 13:54:34 +04:00
|
|
|
esac
|
2005-08-26 05:15:32 +04:00
|
|
|
|
|
|
|
# If the original head was empty (i.e. no "master" yet), or
|
|
|
|
# if we were told not to worry, we do not have to check.
|
|
|
|
case ",$update_head_ok,$orig_head," in
|
|
|
|
*,, | t,* )
|
|
|
|
;;
|
|
|
|
*)
|
2005-09-28 05:14:27 +04:00
|
|
|
curr_head=$(git-rev-parse --verify HEAD 2>/dev/null)
|
2005-08-26 05:15:32 +04:00
|
|
|
if test "$curr_head" != "$orig_head"
|
|
|
|
then
|
2005-09-28 05:14:27 +04:00
|
|
|
git-update-ref HEAD "$orig_head"
|
2005-08-26 05:15:32 +04:00
|
|
|
die "Cannot fetch into the current branch."
|
|
|
|
fi
|
|
|
|
;;
|
|
|
|
esac
|