author | Junio C Hamano <junkio@cox.net> | |
Fri, 5 Aug 2005 07:47:56 +0000 (00:47 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 5 Aug 2005 07:47:56 +0000 (00:47 -0700) | ||
commit | 37fde874c2448ae2cd98abe24df2bd2a50aa2cda | |
tree | 840ddec7144dd152792bd982d584db01472cadc6 | tree | snapshot |
parent | b03e2d2091153d239063cfc086a840d74a9eadde | commit | diff |
Fix send-pack for non-commitish tags.
Again I left the v2.6.11-tree tag behind. My bad.
This commit makes sure that we do not barf when pushing a ref
that is a non-commitish tag. You can update a remote ref under
the following conditions:
* You can always use --force.
* Creating a brand new ref is OK.
* If the remote ref is exactly the same as what you are
pushing, it is OK (nothing is pushed).
* You can replace a commitish with another commitish which is a
descendant of it, if you can verify the ancestry between them;
this and the above means you have to have what you are replacing.
* Otherwise you cannot update; you need to use --force.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Again I left the v2.6.11-tree tag behind. My bad.
This commit makes sure that we do not barf when pushing a ref
that is a non-commitish tag. You can update a remote ref under
the following conditions:
* You can always use --force.
* Creating a brand new ref is OK.
* If the remote ref is exactly the same as what you are
pushing, it is OK (nothing is pushed).
* You can replace a commitish with another commitish which is a
descendant of it, if you can verify the ancestry between them;
this and the above means you have to have what you are replacing.
* Otherwise you cannot update; you need to use --force.
Signed-off-by: Junio C Hamano <junkio@cox.net>
commit.c | diff | blob | history | |
send-pack.c | diff | blob | history | |
tag.c | diff | blob | history | |
tag.h | diff | blob | history |