It may be worthwhile reviewing how Git handles ignore files: 1) The user can place an ignore file anywhere in the current directory or any higher directory in the repo tree. NB It would be expected that .gitignore files are under version control and so global to the project (i.e. the settings are transferred during puhs/pull/sync) 2) Ignore patterns can be placed in the repo file $GIT_DIR/info/exclude. This file is *not* transferred when the repo is syncd) 3) A per user ignore file specified by a global setting (mine is $HOME/.gitignore) Obviously not syncd either.
(see http://www.kernel.org/pub/software/scm/git/docs/gitignore.html) Whilst ignore files may not be appropriate for fossil, I think this layered approach is a good design Yes I know, patches welcome :-) -- Alec Clews Personal <[email protected]> Melbourne, Australia. Jabber: [email protected] PGPKey ID: 0x9BBBFC7C blog:http://alecthegeek.wordpress.com/ On Fri, Aug 28, 2009 at 14:37, Michael Richter<[email protected]> wrote: > 2009/8/28 Michael McDaniel <[email protected]> >> >> So, I could add *~ to my .???ignore file and none of >> my gnu emacs backup files would be version controlled. > > I would like to see a feature like this as well, although I think the ignore > list should properly be in the repository proper, perhaps as a local > setting. Having special control files in the checkout directory strikes me > as a way to sow confusion as each person will start to have diverging > .???ignore files. > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
