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 Date: Mon, 30 Nov 2009 22:27:00 +0100 Message-ID: References: <4B140ACF.9090808@gmx.de> <874oob955s.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 1259616472 27436 80.91.229.12 (30 Nov 2009 21:27:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 21:27:52 +0000 (UTC) Cc: 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 22:27:45 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 1NFDmR-0007Dg-K9 for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 22:27:36 +0100 Original-Received: from localhost ([127.0.0.1]:49067 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFDmR-0004pe-2N for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 16:27:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFDmJ-0004p1-IW for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:27:27 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFDmE-0004mm-Mv for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:27:26 -0500 Original-Received: from [199.232.76.173] (port=33464 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFDmE-0004m8-BD for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:27:22 -0500 Original-Received: from mail-yx0-f191.google.com ([209.85.210.191]:38438) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFDmD-00059e-7Q for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:27:21 -0500 Original-Received: by yxe29 with SMTP id 29so3868639yxe.14 for ; Mon, 30 Nov 2009 13:27:20 -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=lCWPF6LvQoHUQWazMCVFuVCQZtIirOb24UHWsNeKWD8=; b=c02KXktpH6/h4pwFLagxBW7btQ/AcI1G96q+hoapJ99aWJczGaJQvgAUCsECl9zTNN Vgu18OyYRwZrKCDWt48bwGQ9hF+SBNK2bLYthQR64SG8x7skFUL/OyejoK/YrzF3fmER 9Zmv9zeVoh69dPFBp755BIob7V6il0eq5rvTc= 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=u57aT8V8Mon/HUT3BBPzEbriH7cwIOu/cc6H7fLILmt2PSTyO4dh0CJjgEazFZbBIg KEdtZBJIhLAU9uvFp2mWw3bBaRMJ+vAbMbQ/+cMrHSwJgC5dnYpva6kVm4RJxOs93JNZ 0e1EdouFJiAm+kp6IqncDJ9PAfgmMPon/3hR8= Original-Received: by 10.101.191.10 with SMTP id t10mr871284anp.71.1259616440103; Mon, 30 Nov 2009 13:27:20 -0800 (PST) In-Reply-To: <874oob955s.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:117998 Archived-At: On Mon, Nov 30, 2009 at 8:35 PM, =C3=93scar Fuentes wrote: > 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? Why do I have to copy the files? Why can't this setup be done with the already existing files? >> 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? Partly, but there is another problem. I thought I would get some help with that since there are some helpful guys here who can teach me a bit. Maybe I should tell you that problem... I have put my little elisp library nXhtml at Launchpad so you can download it with bzr. However a lot of people already have nXhtml installed, but it was not checked out from Launchpad. It came from a zip file or similar. Now I believed that since bzr is a new modern system it would of course have thought of that kind of situation. I am a bad manual reader so I had probably just not understod how to do it... - it is of course possible to update the files using only bzr. That was my believe. Maybe my believe is crazy. Maybe this should not be possible for some reason. But I do not understand why. > 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. I am grateful for the explanations you and others have given for this. I am just surprised that I have to copy the files. It certainly makes the process slower in several ways. I have to do more. And there will be more network traffic etc. > 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" Thanks. > 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 will think about it ;-) > 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. > > -- > =C3=93scar