From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Sat, 21 Nov 2009 18:08:17 +0100 Message-ID: <87r5rr6c1q.fsf@telefonica.net> References: <87vdhfpil2.fsf@red-bean.com> <87einvxy9c.fsf@red-bean.com> <20091118230952.GB908@muc.de> <87my2jw05z.fsf@red-bean.com> <83skc9pbf7.fsf@gnu.org> <87iqd5vw5n.fsf@red-bean.com> <877htl53tc.fsf@telefonica.net> <871vjs6ci7.fsf@telefonica.net> <87d43c4f1e.fsf@telefonica.net> <837htkoxy8.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1258823439 4101 80.91.229.12 (21 Nov 2009 17:10:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Nov 2009 17:10:39 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 21 18:10:32 2009 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 1NBtTj-0000As-Hu for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 18:10:31 +0100 Original-Received: from localhost ([127.0.0.1]:47801 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBtTi-0005IU-WF for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 12:10:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBtTe-0005IH-7i for emacs-devel@gnu.org; Sat, 21 Nov 2009 12:10:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBtTZ-0005CO-ED for emacs-devel@gnu.org; Sat, 21 Nov 2009 12:10:25 -0500 Original-Received: from [199.232.76.173] (port=58671 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBtTZ-0005CF-Bb for emacs-devel@gnu.org; Sat, 21 Nov 2009 12:10:21 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:52838) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NBtTY-0007QE-GK for emacs-devel@gnu.org; Sat, 21 Nov 2009 12:10:20 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NBtTQ-0008UB-BB for emacs-devel@gnu.org; Sat, 21 Nov 2009 18:10:17 +0100 Original-Received: from 153.red-88-24-228.staticip.rima-tde.net ([88.24.228.153]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Nov 2009 18:10:12 +0100 Original-Received: from ofv by 153.red-88-24-228.staticip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Nov 2009 18:10:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 83 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 153.red-88-24-228.staticip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:jatlXS5OEIaas63gWMc4dAlBSGo= 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:117452 Archived-At: Eli Zaretskii writes: >> You got that wrong. I was not suggesting that he shall create a remote >> branch. `bzr branch URL' creates a local branch: >> >> bzr branch http://somehost.com/repo/bzr/project/trunk >> >> creates a branch which is a clone of the branch pointed by the URL, but >> on your local machine. >> >> Besides, using a shared repository is just a disk&time saving trick, it >> doesn't affect the workflow otherwise. > > So when to use a shared repository and when not? Could you please > give some details that would allow one to make up her mind? As shared repositories saves disk space and speeds up branch creation, it is advisable to use them. Of course, a shared repo imposes that the branches shall be on a certain, fixed location on your filesystem hierarchy (i.e. within the directory that contains the shared repo). It is not good idea to move branches around when they reside on a shared repo (as other branches may contain internal pointers to them). I don't think this is a problem for most users, though. >> So he needs to download the Emacs branch. `bzr branch URL' is one way, >> downloading a tarball is another. You can put the result of `bzr branch' >> directly on a shared repo. > > What does the last sentence mean, in terms of commands that I would > need to issue? # Create a shared repo on a directory named `emacs-dev': bzr init-repo emacs-dev cd emacs-dev # Now create our own mirror of the emacs master development branch: bzr branch URL-TO-EMACS-DEV-BRANCH-ON-GNU mirror >From now on, within the same `emacs-dev' directory, you use `bzr branch' again for creating branches for hacking, etc. bzr branch mirror my-sandbox >> If you downloaded the tarball and want to put >> your mirror branch on a shared repository you need two extra steps >> besides downloading and untarring. The first is precisely `bzr branch', >> but this time locally using the tarball'ed branch as the parent, and the >> second step is configuring the resulting branch for using the remote >> emacs branch at GNU as its parent. > > Again, please tell more details. Showing the commands or pointing to > the bzr docs would be a good start. Without some additional info, all > this sounds to me like a conversation in a language I don't > understand. Please try to make it more understandable for someone who > does not have your level of knowledge and experience with bzr, but > needs nonetheless to make up her mind about the way to set up and use > bzr without wasting too much time. Thanks in advance. A branch is self contained. This means that it really doesn't matter much if you obtain your mirror branch directly from GNU or from any other mirror of the GNU master branch. By downloading and untarring a tarball with a copy of the GNU master branch, you alreday did the equivalent of `bzr branch URL-TO-GNU-MASTER-BRANCH'. However, that branch does not reside on a shared repo and, AFAIK, it is not right to move the directory where your untarred branch resides to the directory of a bzr shared repo. The solution is to `bzr branch' your untarred branch to the shared repo: # Let's suppose that your untarred branch is on emacs-untarred/ # We start by creating a shared repo: bzr init-repo emacs-dev # Now we branch (i.e. clone) the untarred branch to our shared repo: cd emacs-dev bzr branch ../emacs-untarred mirror # That's it. We can remove the untarred branch. # As the tarball may be a bit out of date, we get now the most recent # changes: cd mirror bzr update -- Óscar