Can a standalone repository exist in a subdir of another standalone repos?

Asked by Kevin Sherrill

I have a problem with TortoiseBZR not behaving correctly with the context menu options. I have a standalone repos in a directory I'll call C:/Flash/SlotA and in a subdirectory I created a standalone repos called SlotB aka C:/Flash/SlotA/SlotB. After creating the SlotB repos and adding some files, I find the + icons don't display over the files. And I can't get a commit option in any of the context menus. It's like Tortoise is assuming I'm in a branch of the parent repos and only offers the "Branch/Checkout..." option.

It looks like my only option is to flatten these directories and have them all at the same level if I want to use the context menus. Anyone know of a workaround or fix for this? I specifically made them standalone directories but they don't behave that way.

Question information

Language:
English Edit question
Status:
Solved
For:
TortoiseBZR Edit question
Assignee:
No assignee Edit question
Solved by:
Kevin Sherrill
Solved:
Last query:
Last reply:
Revision history for this message
John A Meinel (jameinel) said :
#1

I don't know why TortoiseBZR would be confused, as bzr itself supports
nesting repositories just fine.

John
=:->
On Mar 13, 2013 4:50 AM, "Kevin Sherrill" <
<email address hidden>> wrote:

> New question #224099 on TortoiseBZR:
> https://answers.launchpad.net/tortoisebzr/+question/224099
>
>
> I have a problem with TortoiseBZR not behaving correctly with the context
> menu options. I have a standalone repos in a directory I'll call
> C:/Flash/SlotA and in a subdirectory I created a standalone repos called
> SlotB aka C:/Flash/SlotA/SlotB. After creating the SlotB repos and adding
> some files, I find the + icons don't display over the files. And I can't
> get a commit option in any of the context menus. It's like Tortoise is
> assuming I'm in a branch of the parent repos and only offers the
> "Branch/Checkout..." option.
>
> It looks like my only option is to flatten these directories and have them
> all at the same level if I want to use the context menus. Anyone know of a
> workaround or fix for this? I specifically made them standalone directories
> but they don't behave that way.
>
>
> --
> You received this question notification because you are a member of
> TortoiseBZR Developers, which is an answer contact for TortoiseBZR.
>

Revision history for this message
Kevin Sherrill (kevinsh) said :
#2

Problem continues to plague me, but I discovered an interesting bit of info:

Does tortoiseBzr look at the directory contents to make a decision on whether or not the directory should be treated as the "root" of a standalone repository?

Because when putting a Flash Pro project under bazaar control there are no ".settings" or ".project" files or subdirectories, just the Flash .fla file. And yet if I create a Flash Builder project within that same directory, which does create such files and directories, tortoiseBZR begins to function correctly.

Hope that info helps.

Revision history for this message
John A Meinel (jameinel) said :
#3

I would guess that creating the .project files doesn't have an effect on tbzr. I would actually guess that it had cached some amount of directory lookups, and just took some time for it to scan again.

Revision history for this message
IWATA Hidetaka (hid-iwata) said :
#4

Sorry, TortoiseBzr does not support nested repos now.

Sometimes, tbzr may show overlays on inner repository, but it is an accidental behavior.

If tbzr find inner repository before outer one, tbzr shows overlays on inner repository.
Otherwise, tbzr treats files in the inner repository as unversioned.

Revision history for this message
Kevin Sherrill (kevinsh) said :
#5

Thanks. That's what I was experiencing. Sometimes the inner repos would show proper overlays and correct context menus and other times it wouldn't. If I pulled the inner repository out into a non-nested directory it was fine.

The last time it switched and started working, I had just created a Flash Builder project in the inner directory. So I concluded that had played a role somehow.

Ah well, looks like I'm going to be rearrange my projects. I originally had a lobby project and the sub-games nested under it, but I suppose I can make them all sibling directories.