| commit | 098e711e6c0d123dff2f38d6b804ec632ad7dd78 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Mon, 2 Jul 2007 02:00:08 +0000 (1 19:00 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 3 Jul 2007 03:57:45 +0000 (2 20:57 -0700) | ||
| tree | 8eff204173270918a0fd53a7b6c589708941a22e | treesnapshot (tar.gz zip) |
| parent | b941ffac506d3f57246e46a8913da614e62a1d48 | commitdiff |
"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>
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>
| remote.c | diffblobblamehistory |