Hello, What about?
fossil ignore file1 file2 ... In this case, fossil would store the names of the files in the repository. These files would not appear in "fossil extras" and would give an error if "fossil add" fossil ignore directory1 ... directory2 ... the same, but would apply to all files inside that directories (fossil would only store the directory name) ignored files could be considered again by using "fossil rm file1" or "fossil unignore file1" Another interesting addition to fossil would be a "fossil extras" that only gave the extra files inside current directory Ramon Ribó 2010/2/10 Joshua Paine <[email protected]>: > What I could really, really use is a way to persistently ignore files > and entire directories. It's great to keep all your files that shouldn't > be version controlled out of your project dir, but I'm working on > someone else's existing website (converted from CVS to fossil, thanks to > a handy script posted on this list), and it's years too late now to move > the thousands of non-controlled files to a different file tree. > > -- > Joshua Paine > LetterBlock: Web applications built with joy > http://letterblock.com/ > 301-576-1920 > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
