Inner repos

[Marco Canini]

Hi John,
thanks for the fast reply.
I'm playing a bit with bzr since yesterday, I'm happy to know I can do that.
Another question: well maybe it's more than one
Why the push cmd is not shipped with bzr?
I think that for a distributed rcs it's really important to have the push cmd.

Another thing I'm really interested in is the support for plugins.
Now bzr would be really perfect to me if it could support through a plugin 
this use case.
First lemme say that it's fantastic to have only one .bzr directory.
My ideal use of bzr would be to have two branches, one on a backed up server, 
the other on my laptop. The second would be a clone of the first.
However in those branches I would not only keep sources, or in general textual 
files, but also binary files.
Except in rare case I would not be interested to enable revision control for 
those binary files, however I would like them to be known by bzr so that they 
can be synched between server and laptop.
I know it's kinda a mix between rsync or unison and a rcs, but that would be 
great for me.
Do you think it's feasible? Or does it already exist?

Thanks

On Saturday 31 December 2005 17:02, John A Meinel wrote:
> Marco Canini wrote:
> > Hi all, I'm new to bzr.
> > I would like to know if bzr handles inner repositories?
> > I mean if I have a parent repository can i have inside its directory
> > other repositories as subdirs.
> > Thanks
>
> We would generally call these branches. But yes you can do so.
>
> If I do:
>
> $ mkdir a
> $ cd a
> $ bzr init
> $ mkdir b
> $ cd b
> $ bzr init
> $ cd ..
> $ bzr status
> unknown:
>   b/
>
> Basically, you have a couple of options. 'b' is unknown because it looks
> like a directory which is unversioned to the 'a' branch.
> You can live with the unknown status, or you can ignore it:
> bzr ignore ./b/
>
> In the near future, we will add explicit support for nested branches. To
> the effect that the parent branch can remember what revision the child
> branch was at, and when you do a checkout, it can actually checkout the
> child branches at the correct revision at the same time.
>
> I'm not sure when that will happen, but it is on the todo list. Probably
> in less than 1 year. I'm guessing before bzr hits 1.0.
>
> John
> =:->

-- 
Marco Canini