Ramkumar Ramachandra <artagnon@xxxxxxxxx> writes: > Darren Cook writes: > > 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. > > This is a good suggestion. It already has a way to handle gitlinks > (for submodules), so this seems like a very reasonable feature. I just hope that a suboptimal workflow that I use won't stop working. Currently I have TODO file in gitweb/ subdirectory, which is stored in gitweb/.git repository. Still it doesn't prevent me from "git add"-ing e.g. 'gitweb/gitweb.perl' to git repository itself. -- Jakub Narebski Poland ShadeHawk on #git -- 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