The git clean -e option is more useful than just for stuff that you plan to bring under git control later. It also allows to retain per-user configurations of external tools when using git clean to remove all build results and intermediate files. This leads to the enhancement request described below. Most IDEs (integrated development environments) allow the user to configure various display and debugger options, and store those options in some configuration file. Such user option files should not be under git control in a multi-user environment, because then all users are forced to use the same options. Yet these user option files should not be deleted when the rest of the untracked files are deleted (through git clean), otherwise the user options are lost. git clean -x -d -f -e "pattern" removes all untracked files except those matching the pattern. However, it is cumbersome to specify these patterns every time. It would be more convenient if git clean would read such patterns from a file similar to .gitignore (maybe .gitignoreclean?). Then that file itself could be put under git control and shared with the other developers. I request implementation of this feature. Best regards, Louis Strous -- 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