On Mon, Mar 09, 2015 at 04:06:37PM -0700, William Lasiewicz wrote: > 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 > repository. > 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?
Git doesn't handle users. You can either use the system's way of handling users (what you mention above) or add a git-serving system (gitolite, gitlab, ...) which typically uses SSH configurations to deal with users (one system user, typically called `git`, each developer then registers their own SSH key and the server SW does the right thing). > 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? Again, not done in git, if it's done, it's done in the server SW. Take a look at gitolite or gitlab or ... well, just Google for it! > 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? It sounds like you are forced to use git and now use it in anger... however, language like "real tool" won't make friends on this list ;) "Different strokes for different folks!" I've used p4. I found it to be an absolute pain. I much prefer git. But that's just *me*! Anyway, to solve the issue with access control you have to, again, look at git-serving solutions. I vaguely remember some having sub-repo access control. Here's why I like git better than p4: - Git scales down better; no need to have a server, so I end up version controlling way more stuff than I would have otherwise. - Git let's me share code in various ways; git can produce diffs, git can produce email sets, `git bundle`, I can serve up a repo temporarily for a co-worker to pull a few changes, ... - Git let's me re-arrange (local) history and rebase - Git has gerrit - Git has github and gitlab Well, that's what I can think of at the moment. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus $my_args = shift; system("gcc $my_args"); print "I prefer C\n"; -- Robert Dieterich's contribution to the 2004 Perl Haiku Contest, Haikus in Perl - 'Dishonerable Mention' winner -- 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.
Description: PGP signature