From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Making the tarball with bzr data (was: bzr repository ready?) Date: Mon, 30 Nov 2009 17:34:32 +0100 Message-ID: References: <87iqd5vw5n.fsf@red-bean.com> <87vdh29lfo.fsf@red-bean.com> <83k4xhoo0n.fsf@gnu.org> <87my2dhlko.fsf@telefonica.net> <87r5rpsnfw.fsf@uwakimon.sk.tsukuba.ac.jp> <873a44hbpn.fsf_-_@telefonica.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1259600128 2848 80.91.229.12 (30 Nov 2009 16:55:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 16:55:28 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: =?UTF-8?Q?=C3=93scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 17:55:16 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 1NF9Wu-0007oq-MG for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 17:55:16 +0100 Original-Received: from localhost ([127.0.0.1]:42125 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NF9Wt-0003aQ-TK for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 11:55:15 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NF9DL-0003uh-36 for emacs-devel@gnu.org; Mon, 30 Nov 2009 11:35:04 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NF9DE-0003sb-KN for emacs-devel@gnu.org; Mon, 30 Nov 2009 11:35:01 -0500 Original-Received: from [199.232.76.173] (port=44705 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NF9DD-0003sQ-Nv for emacs-devel@gnu.org; Mon, 30 Nov 2009 11:34:56 -0500 Original-Received: from mail-gx0-f224.google.com ([209.85.217.224]:42973) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NF9DD-000621-Bw for emacs-devel@gnu.org; Mon, 30 Nov 2009 11:34:55 -0500 Original-Received: by gxk24 with SMTP id 24so611180gxk.6 for ; Mon, 30 Nov 2009 08:34:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=5usmMNJNLGLPWKmJyZqG66Ij8qaR/7xg5yhLlD7taig=; b=qKlZibUx5EhRdEWJLUC4uQrUHdWBsf3pnT/swCsy9iAvlZqUKCMAcMxSI5L8Epjon7 igyo4m7S/NYF6Lb9hSLX2zZnpa+TG+xP4p5qxCZmotw8th44uCYGO3Kp3Jj90orbK4Dg /DnBTtAJy+4Hr83v0XaknBeRosnUzN7rqZnoc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=FCM57kmbkZtPpP+Fow5pvKJINCYE7SFeAX+F77vMAZ9mGZ1IiymNUuBfOkeFCRJ9XM 1baZpMV7WNs0MRE5PufXlG8lfYM+aqwRK7a5wFC6cB0Vu+mOZCC0FOazExEUDhXcd4HI 3ky6rLLO9dQU9xy+iHl3dL4T6Pn1awHDXZoJE= Original-Received: by 10.101.186.22 with SMTP id n22mr1541749anp.194.1259598893907; Mon, 30 Nov 2009 08:34:53 -0800 (PST) In-Reply-To: <873a44hbpn.fsf_-_@telefonica.net> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:117973 Archived-At: On Tue, Nov 24, 2009 at 3:56 AM, =C3=93scar Fuentes wrote: > Stefan Monnier writes: > >> But the hard part is to integrate those 3 starting points with the >> "wget+untar" approach. > > There is a very simple & safe method for creating a tarball that just > requires untarring at the other end. > > First, create a bound branch of `trunk' on a shared repository [1]: > > bzr init-repo emacs-repo > bzr checkout http://bzr.savannah.gnu.org/r/emacs/trunk > > Now, the process of creating the tarball is: > > cd emacs-repo/trunk > bzr update > cd ../.. > tar the emacs-repo directory > > The user just needs to download and untar to get a shared repository > containing `trunk' with read-only access to the GNU repository. A `bzr > update' is enough to get the latest changes and thus have a mirror of > the branch on the GNU repository. > > If the user is an emacs hacker with write access rights, he does: > > cd emacs-repo/trunk > bzr unbind > bzr bind sftp://bzr.savannah.gnu.org/r/emacs/trunk > > And he is ready to start committing. [2] > > If the user needs access to other branches, obtaining them with bazaar > just requires a few minutes, as only those revisions which are not > common with `trunk' will be downloaded. > > If the user prefers other workflows, he has everything he needs, as he > can create branches from the mirror bound branch or unbind the mirror > branch, so this method is not restricted to the "bound work branch" > workflow. If I already have all the Emacs files locally (possibly with some changes) how do I do to make this a bazaar thing? (This must be the most common situation, or?)