> 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.
Not to mention, not every language supports keeping files out of the source directory and in not all cases do you want to. Take a scripting language, for example. I always have a few little scripts here and there that require to be in the same directory as the others and do tasks such as build a package and upload it to my website or a temporary location. I don't want things like that in the repo, yet they are always there and in the way. On projects that can be built out of the source directory, it's not always convenient to keep it out of the project directory. Many of my projects have a directory structure such as: C:/Projects/Abc/src/ C:/Projects/Abc/docs/ C:/Projects/Abc/build/ C:/Projects/Abc/tmp/ C:/Projects/Abc/_FOSSIL_ I don't want tmp nor build in the repo but I don't want to make C:/Projects/Abc_build either. Further, on almost all of my projects, I have in the root project directory CHANGES.txt. I use this file to record my changes that I make in between commits so that when I commit, everything I want note in the commit log is there. Well, CHANGES.txt is not in the repo of course. Another example is again with a scripting language. We have configuration files. One dev might be connecting to their local pgsql database server as johndoe, another may connect to their local box as snoopy... who knows. So, there is a config, right there in the source directory, so when we code we have: source config.tcl i.e. in the same directory as the source. Again, we don't want config.tcl in the repo because it's taylored to that exact use, maybe even containing path information so it's for that exact directory even. There are thousands of legitimate reasons why to have a non-versioned file in your projects directory and when you have some, it makes the extras command useless, unless you want to always weed through the list trying to figure out what you need to add or not add. Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
