converting standalone branches to shared ones...

[Matthew D. Fuller]

On Mon, Feb 20, 2006 at 11:32:46AM +1100 I heard the voice of
Robert Collins, and lo! it spake thus:
> 
> uhm, there are related issue there sure. 

Just making sure it's in mind; moving "into" a repository should be
pretty much the same no matter where the repo is, and moving "out"
should probably be pretty closely related to that.

Maybe it should be a "bzr shove" and "bzr yank"; it's like a
push/pull, except with enough force to take the current working tree's
branch pointer with it.  ;)


> But its not a 'branch' operation - we are not creating a new line of
> development, we are changing the storage of an existing line of
> development. VERY different intent there, and I think its confusing
> to say to people 'make a new line of development to optimise your
> storage use'.

Well, it's confusing to say to people "make a new line of development
to keep a local mirror", too.  (Yeah, I know they aren't really
analogous)

I guess it's more a split on whether "branch" is the "make a branch"
command, or the "manipulate a branch" command.  I'm thinking along the
lines of "branch --delete" from a repo, so a "branch --put-elsewhere"
would fit along side that.  But then, if deleting a branch falls under
a different command, relocating it would too.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.