Bound branch implementation

[Jan Hudec]

On Mon, Nov 14, 2005 at 23:24:41 -0600, John A Meinel wrote:
> I think your idea is generally okay, but I think you are overlooking my
> preferred use case.
> 
> I publish an archive on my server. I make a bound copy of that archive
> on my laptop. And I create a checkout from my laptop archive, into my
> working directory.
> 
> This gives me locally shared storage, so I don't take a lot of space on
> my laptop, it allows me to work offline if I need to, and it generally
> keeps things published on my server.
> 
> This means that I have a checkout of a bound branch. So I need a command
> to handle the checkout, and one to handle the branch.
> 
> Now, you could argue that if I updated one, I'm going to update the
> other. And I can agree that I don't see much utility in saying "update
> the branch, but not the checkout".
> But there are 3 objects in this system, the local checkout, the local
> branch, and the remote branch.

I'd even like to see if you could have a chain of bound branches. Branch
A on server somewhere far, branch B locally in the office, bound to A
and branch C on work station, bound to B. Though of course commit always
needs to go down all the way to A.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051115/e9efd947/attachment.pgp