3 questions.  Thanks in advance for reading this and to whoever answers my 
3 questions.

I am the release manager and we have perforce but we inherited a GIT 
So far about 20 developers access this which is done through creating a ssh 
key and then adding that key on the machine where we have git.
Everyone logs in through the same user "git".  Everything is at Git\home, 
which contains about 25 .git directories.
Telling who checked in files is on the honor system.
As far as I can tell,  setting up a git user is done by adding a user to 
the machine.
Is this really how this is done for this?
The first thing I want to do is give everyone their own user name so code 
access could be restricted to the areas that are needed.  Is this something 
not done in GIT?

So far I can't come up with a reason why you would use this instead of a 
real tool,  but we don't have perforce licenses to add for all these people 
and the bosses want me to look in to taking our perforce which has 
substantial automation in builds and deploys and converting it to this tool 
which looks to be as sophisticated as the old file based stuff that was 
used 15 years ago.
What could be benefited from using this?

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to