Steffen Prohaska [off-list ref] writes:
On Oct 28, 2007, at 8:28 AM, Junio C Hamano wrote:
quoted
Steffen Prohaska [off-list ref] writes:
quoted
This teaches "push <remote> HEAD" to resolve HEAD on the local
side to its real ref name, e.g. refs/heads/master, and then
use the real ref name on the remote side to search a matching
remote ref.
This probably is a good idea.
I'll add an even shorter shorthand: "git push HEAD" will push
the current branch to its default remote.
Ugh, that looks way too magicky. The first parameter to push if
one ever exists has _always_ been the remote, and the above
breaks it.
Please don't.
On Oct 28, 2007, at 4:40 PM, Junio C Hamano wrote:
Steffen Prohaska [off-list ref] writes:
quoted
On Oct 28, 2007, at 8:28 AM, Junio C Hamano wrote:
quoted
Steffen Prohaska [off-list ref] writes:
quoted
This teaches "push <remote> HEAD" to resolve HEAD on the local
side to its real ref name, e.g. refs/heads/master, and then
use the real ref name on the remote side to search a matching
remote ref.
This probably is a good idea.
I'll add an even shorter shorthand: "git push HEAD" will push
the current branch to its default remote.
Ugh, that looks way too magicky. The first parameter to push if
one ever exists has _always_ been the remote, and the above
breaks it.
Yes. It breaks setups that have a remote named HEAD.
Please don't.
I already did it -- it was too easy. But it's a separate patch.
So it can easily be skipped.
What would you propose for pushing only the current branch to
its default remote repository? All information is there. Only
a way to tell push to restrict push to the current branch
is missing. Would you prefer something like
"git push --only-current-branch"?
Steffen