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... > If your workflow is such that incorrect commits are sometimes > generated given either policy, the system should ask you which you mean. Leave it alone. At least it will work the same always. Consistency is good. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513 - 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