From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Making the tarball with bzr data Date: Mon, 30 Nov 2009 16:50:44 -0500 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=us-ascii X-Trace: ger.gmane.org 1259617958 32632 80.91.229.12 (30 Nov 2009 21:52:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 21:52:38 +0000 (UTC) Cc: =?iso-8859-1?Q?=D3scar?= Fuentes , emacs-devel@gnu.org To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 22:52:31 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 1NFEAX-0001IM-QR for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 22:52:30 +0100 Original-Received: from localhost ([127.0.0.1]:49758 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFEAX-0001v3-I8 for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 16:52:29 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFEAR-0001ue-Nl for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:52:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFEAM-0001u8-Fe for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:52:22 -0500 Original-Received: from [199.232.76.173] (port=56058 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFEAM-0001u5-BS for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:52:18 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:54347) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFEAL-0007bp-Ue for emacs-devel@gnu.org; Mon, 30 Nov 2009 16:52:18 -0500 Original-Received: from faina.iro.umontreal.ca (faina.iro.umontreal.ca [132.204.26.177]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id nAULoisu031608; Mon, 30 Nov 2009 16:50:44 -0500 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id C511D3A280; Mon, 30 Nov 2009 16:50:44 -0500 (EST) In-Reply-To: (Lennart Borgman's message of "Mon, 30 Nov 2009 22:27:00 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV3417=0 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:117999 Archived-At: > Why do I have to copy the files? Because the files are but a small part of the data that Bzr will want. > Why can't this setup be done with the already existing files? It can, but then you need to know which Bzr revision corresponds to the files you have. > 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. That is the case if your zip file is a zip of the checkout Bzr tree (probably a lightweight checkout so it isn't bloated by a complete copy of the whole history), in which case it'll include a .bzr directory with the necessary metadata. Stefan