summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2007-07-01 19:00:08 -0700
committerJunio C Hamano <gitster@pobox.com>2007-07-02 20:57:45 -0700
commit098e711e6c0d123dff2f38d6b804ec632ad7dd78 (patch)
tree8eff204173270918a0fd53a7b6c589708941a22e
parentb941ffac506d3f57246e46a8913da614e62a1d48 (diff)
downloadgit-098e711e6c0d123dff2f38d6b804ec632ad7dd78.tar.gz
"git-push $URL" without refspecs pushes only matching branches
When "git push" is run without any refspec (neither on the command line nor in the config), we used to push "matching refs" in the sense that anything under refs/ hierarchy that exist on both ends were updated. This used to be a sane default for publishing your repository to another back when we did not have refs/remotes/ hierarchy, but it does not make much sense these days. This changes the semantics to push only "matching branches". Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--remote.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/remote.c b/remote.c
index 500ca4d968..cf98a44367 100644
--- a/remote.c
+++ b/remote.c
@@ -544,6 +544,13 @@ int match_refs(struct ref *src, struct ref *dst, struct ref ***dst_tail,
if (!pat)
continue;
}
+ else if (prefixcmp(src->name, "refs/heads/"))
+ /*
+ * "matching refs"; traditionally we pushed everything
+ * including refs outside refs/heads/ hierarchy, but
+ * that does not make much sense these days.
+ */
+ continue;
if (pat) {
const char *dst_side = pat->dst ? pat->dst : pat->src;