I think a good solution here would be to add the ability for Fossil to support a .ignored or track ignored files in the db. Then, upon commit, the log entry generated for you to edit (this wouldn't work when using -m "abc") would include a list of files not tracked (not meeting the ignored file list of course).
Maybe when using -m, there could be a warning. This warning should be an option you can enable/disable. Jeremy > Problem > > I forget to add in new files that I create. This leads to me > creating one or more check-ins that aren't a complete > representation of the working set of files. Worse, the new files > are often the ones that I'm working on most actively because > they're new. > > > Suggestion > > Could fossil flag these untracked files to me, and in fact, not > allow me to check-in until I've either added the files to the > project, or told fossil that I don't want them added? > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
