On Mon, 15 Jan 2007, Horst H. von Brand wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > An config option to prohibit committing with untracked files should be > > easy to add. > > Right. And that will annoy the heck out of people who have random litter > left behind, so their fingers will go "git clean; git commit -a" and then > "OOoops!!!". If they can't read the commit message template in the first > place, or train their fingers to "git add" new files immediately... Or they can avoid enabling the config option if it's not actually helpful to them. I don't think it should be the default behavior, but I think it should be available to people who tend to make the mistake Shawn described. For that matter, it would be nice to have an option for filename patterns that shouldn't be left untracked. I end up with plenty of junk, but none of it is *.c or *.h, unless the file is one I put in .gitignore. Actually, a "git ignore" command that adds things to .gitignore (like 'for i in "$*"; do echo $i >> .gitignore; done; git-update-index --add .gitignore') would probably also be helpful. All of the files in my directories are one of (1) Things everybody wants to ignore, because they're build system output or common backup file patterns, (2) Things that should be tracked, because they're source, and (3) Things that shouldn't be tracked in the project, but which I want to hang on to, like interesting debugging output. -Daniel *This .sig left intentionally blank* - 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