Re: Problem with a push
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 11, 2007, 23:49 UTC
- Message-ID
- <7vhcpenjao.fsf@assigned-by-dhcp.pobox.com>
- In-Reply-To
- <alpine.LFD.0.98.0706111556160.14121@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> What was the command line? In particular, was this a "git push --all" or > something? I think we should make sure that we do *not* push remotes by > default (and if you really *really* want to push remotes, you'd have to > specify them explicitly).
I suspect that people (probably rightfully) just say "git push" without saying anything else, and the so-useful-for-old-timers default "matching refs" behaviour bites them when they do so.
If you create a non-bare clone, clone from that, and then try to push from the second generation clone to the first generation non-bare clone, surely there will be "matching" remotes/origin/, except that they are not really matching X-<.