2 messages, 1 author, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:17
sean [off-list ref] writes:
What about just always excluding the origin branch from being implicitly pushed; even if it does exist in both repositories? In the rare cases where it is actually desired to be pushed, it can be done explicitly.
The problem is "origin" is just a Porcelain convention and we would not want to teach that to the core level, so that will not fly.
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:17
Junio C Hamano [off-list ref] writes:
sean [off-list ref] writes:quoted
What about just always excluding the origin branch from being implicitly pushed; even if it does exist in both repositories? In the rare cases where it is actually desired to be pushed, it can be done explicitly.The problem is "origin" is just a Porcelain convention and we would not want to teach that to the core level, so that will not fly.
One improvement that can be done is to update "git clone --bare" so that it does not create "origin", which is more or less pointless for such a "distribution point" repository. This reminds me that I need to deprecate --naked and introduce --bare to the clone command...