summaryrefslogtreecommitdiff
path: root/remote.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-03-04 22:36:33 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-03-04 23:01:11 (GMT)
commit703e8e65c8e3781642ae609117818c42496adf24 (patch)
tree68958c7ec8d3c6de9f28c76e16074798ae053579 /remote.c
parente6363a4992637267ef212d7c709ede17d4122e0d (diff)
downloadgit-703e8e65c8e3781642ae609117818c42496adf24.zip
git-703e8e65c8e3781642ae609117818c42496adf24.tar.gz
git-703e8e65c8e3781642ae609117818c42496adf24.tar.bz2
match_push_refs(): nobody sets src->peer_ref anymore
In ancient times, we used to disallow the same source ref to be pushed to more than one places, e.g. "git push there master:master master:naster" was disallowed. We later lifted this restriction with db27ee63929f (send-pack: allow the same source to be pushed more than once., 2005-08-06) and there no longer is anybody that sets peer_ref for the source side of the ref list in the push codepath since then. Remove one leftover no-op in a loop that iterates over the source side of ref list (i.e. our local ref) to see if it can/should be sent to a matching destination ref while skipping ones that is marked with peer_ref (which will never exist, so we do not skip anything). Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'remote.c')
-rw-r--r--remote.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/remote.c b/remote.c
index ca1f8f2..f065603 100644
--- a/remote.c
+++ b/remote.c
@@ -1227,9 +1227,6 @@ int match_push_refs(struct ref *src, struct ref **dst,
const struct refspec *pat = NULL;
char *dst_name;
- if (ref->peer_ref)
- continue;
-
dst_name = get_ref_match(rs, nr_refspec, ref, send_mirror, FROM_SRC, &pat);
if (!dst_name)
continue;