Demonstration Help.

[Eric Berry]

>
>
> Yes, when Bazaar creates the local branch copy of ProjectA/main,
> ProjectB/main, etc., it will notice that the local target directory is
> below a shared repository directory in the filesystem hierarchy, so it
> will store all the actual revision data in the shared repo, making the
> actual branch data very small (on the order of 100 KiB), plus the
> working tree since you implicitly specified to create working trees as
> well.
>

Cool. :) That's really nifty. In regards to the working tree, I was under
the impression that if I had specified --no-trees, I would not be able to
create working trees under the shared repo. Is that incorrect?

So, I could have done:
[code current_dir="~/development/projects"]
bzr init-repo --no-trees .
bzr branch ftp://[host]/ProjectA/main ProjectA
bzr branch ftp://[host]/ProjectB/main ProjectB
bzr branch ftp://[host]/ProjectC/main ProjectC
[/code]

And spared myself the extra space of the working tree for each local branch?
Would I still be able to see all the files, and work directly on each local
branch? Or would I then have to branch, or checkout, somewhere else from
those local branches?


>
> Also, in the case above, where you have 3 apparently "unrelated" (from
> the perspective of Bazaar history, at least) branches being stored in a
> single shared repository, that is fine and can mean easier
> administration for you -- the shared repo really acts fairly
> transparently.
>

Very nice.

Thanks,
Eric

-- 
Learn from the past. Live in the present. Plan for the future.
11101000
http://www.townsfolkdesigns.com/blogs/elberry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090220/6c167d49/attachment.htm