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 23:33:58 +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 X-Trace: ger.gmane.org 1259620791 9200 80.91.229.12 (30 Nov 2009 22:39:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 22:39:51 +0000 (UTC) Cc: =?UTF-8?Q?=C3=93scar_Fuentes?= , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 23:39: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 1NFEuH-0005F2-0P for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 23:39:45 +0100 Original-Received: from localhost ([127.0.0.1]:42566 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFEuG-0001we-Hi for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 17:39:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFEp5-0007j0-T4 for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:34:23 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFEp1-0007gl-Q7 for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:34:23 -0500 Original-Received: from [199.232.76.173] (port=48169 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFEp1-0007ge-Mn for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:34:19 -0500 Original-Received: from mail-yx0-f191.google.com ([209.85.210.191]:37418) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFEp1-0002pZ-AO for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:34:19 -0500 Original-Received: by yxe29 with SMTP id 29so4021633yxe.14 for ; Mon, 30 Nov 2009 14:34:18 -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; bh=p/tDhOCbYpRPTUKL37uJPRMu/FjGJztCHGuWEjwR0ro=; b=nPateotxQ34tOmXun7NqFlzxzzSd17+U2PyZ7W1Z2RQ+hVstg237syBnHecDG5bzoZ 0l61TaqqK84IMvB5Jm093MonQWXe/8FbfnEaA1hSqDsQIcgSPByK69uyhd9gZhsVsAe2 Bo49zOhnNwvjuQuASEjOg8A4P6dZc16Yqg96Y= 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; b=Kr6SBd0791hO33DVkpIas03O2trTKnb2Hnrk0b3BrOVEXHxaBuA4N8/HCLAeLfeoni jNDEazkuaboe/fy0Geoc8K6hi4NBb7aY2ipzyqT9GLHvZRH4n1s6XWMdDfdFHqX74ECe rN85qAFdUfygbpQvOL80313zxmpN312lG/Z8E= Original-Received: by 10.101.151.30 with SMTP id d30mr922910ano.135.1259620458069; Mon, 30 Nov 2009 14:34:18 -0800 (PST) In-Reply-To: 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:118002 Archived-At: On Mon, Nov 30, 2009 at 10:50 PM, Stefan Monnier wrote: >> Why do I have to copy the files? > > Because the files are but a small part of the data that Bzr will want. Does not that depend on if I want/need the history data locally? If I do not want to use it at all? >> 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. In that case wouldn't it be possible to let bzr assume that the my files are checked out from the current revision and then changed? (As a separate command of course, for use in those circumstances where it might make sense.) >> 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. Thanks.