Converting standalone branch to inside-repo branch?

Hendy Irawan hendy at rainbowpurple.com
Thu Sep 13 12:42:09 BST 2007


Andrew Cowie wrote:
> On Wed, 2007-09-12 at 18:15 +0200, Nicholas Allen wrote:
>   
>> Perhaps it would be nice if init-repo could detect there were existing 
>> branches under it and ask the user if they want to move the history into 
>> the shared repo. 
>>     
>
> I ran into this the other day. I agree it would be a cool feature.
>
> You might run into the problem of it being too jealous
>
>  - if you accidentally do `bzr init-repository` in /, you're in for a
> ride; and
>
>  - how many levels down do you go, in the case where people are nesting
> branches in (empty) convenience directories [ie we have
> repository/mainline and repository/hackers/person1/branches and
> repository/hackers/person2/branches, both hackers and person{1,2} are
> empty not branches not "repos"]
>
> still, seems like it could just work, ie "if there are no .bzr
> directories in directories immediately below this one, then don't worry
> about looking for branches' revisions to pull up, just make the new repp
> and get on with it.
>
>   
I'd totally agree with one-level deep (i.e. directly below the repo). 
I'm not sure if anyone would need a two-level deep branch inside a repo, 
but this can be provided via an option.

Besides if they really want, they can symlink it... I'm not sure about 
its implications though.
>> or it could just do it anyway as I can't think of a case where 
>> one would want to keep a branch inside a repo that didn't store its 
>> history in the repo.
>>     
>
> Me neither. Sounds like a sensible default & no need for an option.
>
> AfC
> Sydney
>
>   


-- 
Hendy Irawan
www.hendyirawan.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070913/63ae595e/attachment.htm 


More information about the bazaar mailing list