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: Making the tarball with bzr data Date: Mon, 30 Nov 2009 19:46:53 +0100 Message-ID: <878wdn97fm.fsf@telefonica.net> 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: 8bit X-Trace: ger.gmane.org 1259608142 31303 80.91.229.12 (30 Nov 2009 19:09:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 19:09:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 20:08:55 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 1NFBcE-0004vm-HS for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 20:08:54 +0100 Original-Received: from localhost ([127.0.0.1]:56630 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFBcE-0005Os-7G for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 14:08:54 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFBKt-0004EO-Co for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:50:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFBKj-0003zS-Py for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:50:53 -0500 Original-Received: from [199.232.76.173] (port=59352 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFBKj-0003yo-Ap for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:50:49 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:40890) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NFBKi-0005Sk-OJ for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:50:49 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NFBKg-0005Yl-2O for emacs-devel@gnu.org; Mon, 30 Nov 2009 19:50:46 +0100 Original-Received: from 238.red-83-37-167.dynamicip.rima-tde.net ([83.37.167.238]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 19:50:46 +0100 Original-Received: from ofv by 238.red-83-37-167.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 19:50:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 238.red-83-37-167.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:2IHDwS52skSj1ECpizWYyEAwH+g= 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:117982 Archived-At: Lennart Borgman writes: >> There is a very simple & safe method for creating a tarball that just >> requires untarring at the other end. [snip] > 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?) The most simple solution is to create a working bzr setup as explained on the wiki and then copy the modified files you have on your CVS checkout over the corresponding files on the work branch of the bzr setup. I'm talking here assuming that people will use the workflow documented by Karl and Stephen. BTW, one advantage of the workflow they recommend over the one I documented and CVS (which are equivalent on this specific aspect) is that, when you end your working session, you can commit your changes locally with a comment about its state and what remains to be done. Later, when you come back, read what you put on the last commit and keep hacking. When the work is complete, you push to upstream (with or without the history of your private commits). Another advantage of their workflow is that you don't need to mix the implementation of distint features on the same working source tree. You can easily create your own personal local branches, one for each task you are working on. -- Óscar