On Thu, Aug 15, 2013 at 09:46:49PM -0700, Jimit Modi wrote:
At our company, we are evaulating to migrate to GIT from SVN. Here we are
following a process in which we have the following branch and access
control.
---
| Branch| Purpose
Well the branches do not need to be on the same location/folder/computer.
The devs could push to e.g. /cmdata/git/devs/myproject.git
The tl pulls from devs and pushes to e.g. /cmdata/git/tl/myproject.git
The agm pulls from tl and could push to e.g. /cmdata/git/agm/myproject.git
You just
You could also look into solutions like bitbucket by creating repos and
assigning different access permissions.
Or on a unix server, achieve the same with different repos and unix user access
levels.
All this is defined at process level.
Hope that helps,
HD.
--
You received this message
Hello,
git itself is not capable of authentication and authorization, you will
need a separate software for that. I personally use gitosis, but many
others exist out there. This kind of software is needed only on the
server side, clients can still use good old git client.
Best,
Gergely
On 16 Aug
Thanks. Will look at it and update.
--
Jim(y || it)
On Fri, Aug 16, 2013 at 1:10 PM, Gergely Polonkai gerg...@polonkai.euwrote:
Hello,
git itself is not capable of authentication and authorization, you will
need a separate software for that. I personally use gitosis, but many
others
At our company, we are evaulating to migrate to GIT from SVN. Here we are
following a process in which we have the following branch and access
control.
---
| Branch| Purpose | ACL |