[02:47] <slangasek> vila: strange, I completely missed your ping before.  Did my answer on the bug suffice?
[09:33] <vila> slangasek: good enough for now, I'll prototype something and we can discuss refinements from there
[19:45] <slangasek> vila: ok, cheers :)
[22:49] <sanbar> I have the the directory structure /code, /code/language1, /code/language1/project1, /code/language/project2, etc.  I wish to create a repository in /code, so I used init-repository on /code
[22:50] <sanbar> However, I wish to create my branches in the project directories - do I use init-repository on /code/language, or init (to create a branch on it)?
[22:50] <sanbar> /code/language1*
[22:51] <sanbar> ie, can you have repositories within repositories?
[23:00] <jelmer> hi sanbar
[23:00] <jelmer> sanbar: you can nest repositories, but only the "closest" repository will be used
[23:00] <jelmer> i.e. if you create a repository in /code and a repository in /code/language1, and then create a branch in /code/language1/project1
[23:01] <jelmer> then all revisions will be stored in /code/language1
[23:30] <sanbar> does it do any good to have nested repositories then at all?
[23:31] <sanbar> jelmer: ^
[23:31] <sanbar> (they do seem to be "browsable" using the gui utils, so maybe that is the only benefit?
[23:33] <sanbar> Oh, I get it - you can mix branches/repositories in the "parent" repository.  That would be the benefit, then ...
[23:33] <sanbar> (since it would be "closest" for a branch immediately underneath it ...)
[23:33] <sanbar> jelmer: ^
[23:53] <jelmer> sanbar: sorry, was away for a bit
[23:54] <jelmer> sanbar: no, there isn't much use in having nested repositories