Little hack to web service

Paul Boddie paul.boddie at biotek.uio.no
Thu Oct 11 10:31:23 UTC 2012


On 10/10/12 23:47, Lester Caine wrote:
> Paul Boddie wrote:
>> If you're referring to the hack that allowed repositories in 
>> subdirectories to
>> be hidden until you follow the link for a subdirectory, that was 
>> integrated into
>> Mercurial 2.2, although I think it only got documentation from 2.2.1 
>> (which was
>> probably my fault for forgetting to include any). See the "collapse" 
>> setting for
>> hgweb.
>
> Am I missing some thing ...
> http://lsces.org.uk/hg/ is folding nicely and for 'subdirectories' 
> such as Mercurial component packages the various repositories are 
> listed ( must add a 'back' button on the secondary directories ).

A "back" or "up" button would be nice, yes.

> The problem comes where we have 'sub-repos' properly linked from the 
> top directory.
> bitweaver bundle is the top level repo, and Bitweaver Mirror 
> Repository are the first level sub-repos with 'external' as a second 
> level one.

I'm not sure I understand your description. hgweb will move references 
to repositories located inside other repositories out to the index view 
so that those "subrepositories" will each appear alongside the entry for 
the repository in which they reside.

Is it not the case that "bitweaver bundle" resides at the top-level as a 
repository? Maybe a brief summary of the directory hierarchy might help 
explain the problem a bit more clearly.

> I'm tying this in with the recent improvements to hggit to correctly 
> import the git subrepos and build a local .hgsub but what I need to 
> build is an alternative 'super-project' which can be downloaded from 
> here but uses a different combination of packages.

Are you saying that you don't want the subrepositories to always appear 
next to the parent repositories?

Paul



More information about the Mercurial mailing list