From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Making the tarball with bzr data
Date: Mon, 30 Nov 2009 23:33:58 +0100 [thread overview]
Message-ID: <e01d8a50911301433h3456ee0xb75ea446ec9b5474@mail.gmail.com> (raw)
In-Reply-To: <jwvljhnd6so.fsf-monnier+emacs@gnu.org>
On Mon, Nov 30, 2009 at 10:50 PM, Stefan Monnier
<monnier@iro.umontreal.ca> 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.
next prev parent reply other threads:[~2009-11-30 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 18:11 Making the tarball with bzr data (was: bzr repository ready?) grischka
2009-11-30 18:15 ` Lennart Borgman
2009-11-30 19:35 ` Making the tarball with bzr data Óscar Fuentes
2009-11-30 21:27 ` Lennart Borgman
2009-11-30 21:50 ` Stefan Monnier
2009-11-30 22:33 ` Lennart Borgman [this message]
2009-12-01 3:24 ` Stefan Monnier
2009-11-30 22:44 ` Óscar Fuentes
2009-12-01 2:20 ` Stephen J. Turnbull
2009-12-01 2:40 ` Óscar Fuentes
2009-12-04 18:47 ` Giorgos Keramidas
-- strict thread matches above, loose matches on Subject: below --
2009-10-30 23:38 bzr repository ready? Andreas Schwab
2009-11-20 19:22 ` Karl Fogel
2009-11-21 19:01 ` Glenn Morris
2009-11-22 23:41 ` Karl Fogel
2009-11-23 4:36 ` Eli Zaretskii
2009-11-23 5:11 ` Óscar Fuentes
2009-11-23 5:50 ` Stefan Monnier
2009-11-23 7:35 ` Stephen J. Turnbull
2009-11-23 14:39 ` Stefan Monnier
2009-11-24 2:56 ` Making the tarball with bzr data (was: bzr repository ready?) Óscar Fuentes
2009-11-30 16:34 ` Lennart Borgman
2009-11-30 18:46 ` Making the tarball with bzr data Óscar Fuentes
2009-11-30 18:52 ` Jason Earl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50911301433h3456ee0xb75ea446ec9b5474@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ofv@wanadoo.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.