From: Jens Lehmann Date: Fri, 04 Nov 2011 08:42:13 GMT Subject: Re: Folder level Acces in git Message-ID: <4EB3A565.2040408@web.de> In-Reply-To: <4EB36855.8000802@workspacewhiz.com> Am 04.11.2011 05:21, schrieb Joshua Jensen: > ----- Original Message ----- > From: Eugene Sajine > Date: 11/3/2011 1:28 PM >> Are you sure that the way your have organized the repository is >> actually correct? If you need to manage the access on folder level why >> don't you simply split up the project into several >> repositories/projects which each team is going to work with >> independently? >> >> This seems to me to be much simpler and cleaner solution then any >> other alternative. >> > Submodules are _not_ simple at all. Our organization of nearly 100 developers using Git pretty much let out a collective cheer when we finally removed the submodules. Submodules are an absolute pain to develop within; there are a number of Git mailing list exchanges about that, but I'd be happy to go into great detail if anybody cares. I do care and would appreciate if you could share your problems. > Even submodules that are read-only are a pain as it takes two steps (git pull + git submodule update) to actually get them up to date. Full Ack. I'm working on teaching git to update update the whole work tree - including the submodules - after each checkout, merge, pull, bisect, etc. (which also includes proper support for deletion and re-creation of submodules). What else made using submodules hard for you?