Access control to parts of the repository

Marcin Kasperski Marcin.Kasperski at
Tue Mar 4 06:37:04 CST 2008

> if for example I am a doc writer with access to 
> docs/** and programmers have access to src/**, (...)

then in the first place the question arises whether it does make sense
to keep doc and src within single repository. Keeping docs and code
consistent is nice idea, but once the man who changes the code is not
allowed to fix docs or at least mark that they need to be fixed, the
consistency is no longer here whatever is declared... So if it is really
so that one can work in only one area, then create one mercurial repo
in src, another in docs and bare push permission would suffice.

Or, maybe it is not ACL what is really needed in such case, but
rather some kind of change approval if one touches the files
outside his usual work area... After all, it may happen that
doc writer fixes incorrect error message, or the programmer
patches changed option name in docs, and it seems to be better
idea to force review of such change instead of forbidding such

Bazaar seems to have some related ideas (like )

| Marcin Kasperski   | If Staff, Scope and Schedule are all fixed,
| |  managers will have no options, other than
|                    |               prayer. (Martin)

More information about the Mercurial mailing list