If you are using a shell that follows the unix conventions, dot files&#8212;files that start with a '.' character&#8212;will be ignored unless they are explicitly included.

As an example, if you have files named '.file' and '.faxes', and want to <code>add</code> them using <i>globbing</i> you'd type: <verbatim>    fossil add .f*</verbatim> To get all of your dot files you'd need to be a little trickier, because '.' and '..' are directory names.  In <b>bash</b> you'd use <verbatim>    fossil add .[^.]*</verbatim>

The point is that the dot files are being intercepted by the shell on non-Windows systems, and may be being intercepted on Windows systems&#8212;dot files are a bit problematic and you have to be careful about them.

IMHO:<br>
The <code>CVSIGNORE</code> isn't actually that useful if you are not creating a new repository from a clean source tree, or not using a recursive <code>add</code>.  Until the recursive add fix (see [./tktview?name=e02ffabcda | e02ffabcda]) there wasn't any way to get <b>fossil</b> to add files that were not explicitly requested.  You could still get unwanted files by injudicious file globbing, but that wasn't <b>fossil</b>'s fault.  Personally, I probably won't use recursive add on an 'as is' source tree.  I'll clean it up until it only contains the files I want, then <code>add</code> them, and maybe then copy the, er, "unclean" source tree back.