On Sat, 01 Oct 2011 20:34:43 +0000, Grant wrote: ... > That's true. I hope to be able to give different developers access to > different parts of the code. I really don't know if this will work. Depending on the implementation it may drive away the good devs... Anyway, what I think you need (for the reasons detailed in the svn list) is a setup where the whole project is checked out in the staging area where it can be tested in whatever way. That under a user id different from the dev's. Then you change permissions so that he can only see and edit the files you want him to. This at least eases the problem of having to commit for each test, and gives you a meaningful history. Additionally have sudo permissions to do commits etc. in the staging area. (But still the dev's life will be, erm, suboptimal.) > I just don't want my code to be stolen and I'm trying to find some way > to prevent that from happening. I'm just getting creative. When the one file that you allow access to is server-side code (as opposed to, say, css or client js) then the malevolent dev can use that to read the rest of the staging area anyway. Andreas -- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html