From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bojan Nikolic Newsgroups: gmane.emacs.devel Subject: Re: bzr: public_branch Date: Sun, 10 Jan 2010 23:12:53 +0000 Message-ID: <87my0lh7uy.fsf@bnikolic.co.uk> References: <1tpr5hwwjx.fsf@fencepost.gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1263165221 25960 80.91.229.12 (10 Jan 2010 23:13:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Jan 2010 23:13:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 11 00:13:33 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NU6yR-0007gJ-LT for ged-emacs-devel@m.gmane.org; Mon, 11 Jan 2010 00:13:31 +0100 Original-Received: from localhost ([127.0.0.1]:54937 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NU6yS-0005xS-5O for ged-emacs-devel@m.gmane.org; Sun, 10 Jan 2010 18:13:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NU6yM-0005wd-NF for emacs-devel@gnu.org; Sun, 10 Jan 2010 18:13:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NU6yH-0005uD-V3 for emacs-devel@gnu.org; Sun, 10 Jan 2010 18:13:26 -0500 Original-Received: from [199.232.76.173] (port=44939 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NU6yH-0005u6-Rx for emacs-devel@gnu.org; Sun, 10 Jan 2010 18:13:21 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:58971) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NU6yH-0004WI-If for emacs-devel@gnu.org; Sun, 10 Jan 2010 18:13:21 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NU6yB-0007cl-7g for emacs-devel@gnu.org; Mon, 11 Jan 2010 00:13:15 +0100 Original-Received: from 67.233.107.148 ([67.233.107.148]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jan 2010 00:13:15 +0100 Original-Received: from bojan by 67.233.107.148 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jan 2010 00:13:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67.233.107.148 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:Fo/P53f30O4roGnCBkJ8jnqajNU= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119802 Archived-At: Hi Glen, Both of these concepts are related to the bzr send command, so it is worth reading the help text for this. The bzr send command basically creates a compact data set that describes fully that the changes you have made as a developer. The submit branch defines against what revision those changes should be measured. In other words bzr send sends the changes you made in your branch as compared to the submit branch. In order to calculate those changes, bzr must analyse the submit branch. Therefore it is most efficient for the submit branch to be local. However, in order for others to make sense of your changes their bzr must be able to access the branch against which the changes were calculated. Therefore there must be a public branch with same information as the submit branch. Allowing you to set separate submit and public branches allows you to have the most efficient setup while others still can use the public branch to interpret the changes you send. Best, Bojan -- Bojan Nikolic || http://www.bnikolic.co.uk