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 20:35:59 +0100 Message-ID: <874oob955s.fsf@telefonica.net> References: <4B140ACF.9090808@gmx.de> 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 1259611440 10317 80.91.229.12 (30 Nov 2009 20:04:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 20:04:00 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 21:03:53 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 1NFCTN-0004Y4-VR for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 21:03:50 +0100 Original-Received: from localhost ([127.0.0.1]:43570 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFCTN-0004CQ-NZ for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 15:03:49 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFC6N-0001NN-15 for emacs-devel@gnu.org; Mon, 30 Nov 2009 14:40:03 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFC6I-0001JE-3S for emacs-devel@gnu.org; Mon, 30 Nov 2009 14:40:02 -0500 Original-Received: from [199.232.76.173] (port=43024 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFC6H-0001J7-R5 for emacs-devel@gnu.org; Mon, 30 Nov 2009 14:39:57 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:33993) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NFC6H-0002yF-Ap for emacs-devel@gnu.org; Mon, 30 Nov 2009 14:39:57 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NFC6A-0002X2-Cj for emacs-devel@gnu.org; Mon, 30 Nov 2009 20:39:50 +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 20:39:50 +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 20:39:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 52 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:iwGC9ZTIEtG79CjQqHS+xtZ1fI8= 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:117991 Archived-At: Lennart Borgman writes: > On Mon, Nov 30, 2009 at 7:11 PM, grischka wrote: >>> 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?) >> >> In any case you need to get the official emacs bazaar repository >> first. > > > Thanks grischka. I believe you, but this seems just crazy to me. Why? > What are the reasons for this limitation? How is that a limitation? Let me guess. You are thinking on the CVS checkout you have with all those patches for EmacsW32, right? Well, a brute force solution is to setup your personal bzr Emacs branch and then simply copy everything from your CVS checkout over the bzr branch, or in Windows parlance, copy the contents of the folder lennarts_CVS_checkout over lennarts_bzr_branch, overwriting everythin. You can remove the CVS directories on the bzr branch, as they would be useless once the switch at Savannah is complete. It is a pity that you had no bzr at the time when EmacsW32 was started: you could keep a clean history of the applied patches and publish the branch on something like launchpad or from your webserver. At least, you can start taking advantage from bzr since now: instead of having a checkout with lots of patched files, once you copy them over the bzr branch commit the changes: bzr commit -m "All modifications I have so far" Since this, for applying a new patch: bzr commit -m "Fixes foo" Speaking as somebody who is interested on your modifications, it would be great if you could start from a pristine Emacs working tree and commit one patch at a time, with a descriptive commit message, then publish the branch :-) I'm willing to help you (and anybody else) on the transition to bzr, but please be more specific when describing the problems you are foreseeing. -- Óscar