On 1/23/07, Andre Masella <andre@masella.no-ip.org> wrote:
quoted text
> As I understand it, none of the repository backends allow any per-user
> per-branch access control. SSH and HTTP come the closest with the right
> hooks, but since the repository is writeable by those users, there is little
> to stop them from changing the repository directly.

For this kind of scenario, use one repo per developer with GIT+SSH. It
changes your usage pattern slightly (pull from all repos before push)
but this is easy to setup. And you can even enforce the "won't let you
push unless you are up-to-date with the other repositories" via a
fancy pre-update hook script on the repo.

Or you may chose to have an integration repo _as well_ as public per-dev repos.

quoted text
> So, before I start, I would like to get ideas from others...or be told this is
> a waste of time. Thanks.

Not entirely a waste of time, but there is a very git-style way of
addressing this that will probably save you time...


martin
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html