(Apologies if there is a proper place to report bugs; but I could not find one.) PROBLEM: "git add" adds sub-directories without checking to see if there is already a git repository already there. WHY BAD: This causes files to be in two repositories (leading to a mess if you don't notice for a while...) ONE SOLUTION: When adding files from a directory (except root of the repository, of course) look for a .git subdirectory, and complain if found. Allow --force to override this. MORE SOPHISTICATED: 1. Offer to merge in all that history, followed by removing that old .git subdirectory. 2. Look inside the .git subdirectory to see if the file being added is actually under control there. If not, no need to complain. EXAMPLE OF PROBLEM The problem can arise when people are just dipping their toe into git, and decide to try it on just one directory, then later expand its use to the whole project. mkdir test cd test mkdir settings cd settings git init touch x git add x git commit -m "xx" (time passes) cd .. git init git add settings/ (should complain) Thanks for taking the time to read this, Darren -- Darren Cook, Software Researcher/Developer http://dcook.org/work/ (About me and my work) http://dcook.org/blogs.html (My blogs and articles) -- 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