From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [RFC] Reverting "git push logic change"? Date: Sun, 22 Jan 2006 17:31:22 -0800 Message-ID: <7vacdnafx1.fsf@assigned-by-dhcp.cox.net> References: <20060120225336.GA29206@kroah.com> <7vlkxa30rd.fsf@assigned-by-dhcp.cox.net> <20060121001547.GA30712@kroah.com> <7vfynivx9s.fsf_-_@assigned-by-dhcp.cox.net> <7vr770c8db.fsf@assigned-by-dhcp.cox.net> <7vu0bw9ch7.fsf@assigned-by-dhcp.cox.net> <7vpsmjamgw.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Jan 23 02:31:33 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F0qYK-0007Zn-Ak for gcvg-git@gmane.org; Mon, 23 Jan 2006 02:31:29 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751265AbWAWBbZ (ORCPT ); Sun, 22 Jan 2006 20:31:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751365AbWAWBbZ (ORCPT ); Sun, 22 Jan 2006 20:31:25 -0500 Received: from fed1rmmtao03.cox.net ([68.230.241.36]:29426 "EHLO fed1rmmtao03.cox.net") by vger.kernel.org with ESMTP id S1751265AbWAWBbY (ORCPT ); Sun, 22 Jan 2006 20:31:24 -0500 Received: from assigned-by-dhcp.cox.net ([68.4.9.127]) by fed1rmmtao03.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060123013014.KNVH20875.fed1rmmtao03.cox.net@assigned-by-dhcp.cox.net>; Sun, 22 Jan 2006 20:30:14 -0500 To: sean User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano writes: > sean 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. 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...