I'm a solo developer. I use a folder for each dev project. Each dev project has a tree like - 'admin', 'dev', 'docs' etc. I git each project with the repo in a --separate-git-dir so my backups don't need to include .git repo. I host my own git server as a 'remote' repo server. I use LFS for binary apps (Microsoft Access etc.). I host a repo server because LFS storage would be expensive, as storage of tags, and as a project backup - I rarely if ever clone anything of this server (since I'm the only developer).
I use 3rd party software (Toad, OASIS) that create and manage their own active local git repos and I put their repos on --separate-git-dirs. Their work tree us under \project\dev\<app>\. etc. I 'git submodule add' the 3rd party repos as git 'submodules' under each project. git treats submodules them as independent repos but they're active work folders so I often end up with detached HEAD or pointers to binaries. I've never liked this arrangement of submodules with their working tree inside the main project folder... I've looked into subtrees but there seems to be a lot of command-line learning to be had. Anyone else doing anything like this successfully ie. having applications create nested repos and adding them as submodules? Cheers Greg -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/0902cc58-1fe7-4404-9e64-432d2110bf9en%40googlegroups.com.
