Re: baz format archives in tla

Hi,

Your points about browsing and latency are indeed worth considering.

Thomas Lord <[email protected]> writes:

> And, meanwhile,  the loss of the ability to create empty categories
> and branches
> still strikes me as a loss.   With that capability, an archive
> administrator can
> set up categories and branches and say to a project "your stuff goes
> *here*".
> Without them, the admin can not.

I don't understand the usage pattern you're referring to.  Can you
elaborate?

> And, meanwhile, collapsing the hierarchy as in the baz format makes native
> file system access controls less useful.   One would like to be able
> to say that
> group A has the right to create branches and versions of category X while
> group B has those rights for category Z.   The baz format makes this harder.

Right.  But OTOH, distributed RCS somewhat deprecates filesystem-based
access control: every contributor can create their own archive and merge
from other people's branches as they see fit.  :-)

Thanks,
Ludovic.