2011/8/15 Lluís Batlle i Rossell <virik...@gmail.com> > On Mon, Aug 15, 2011 at 02:41:48AM +0000, altufa...@mail.com wrote: > > Me too like fossil because of simplicity of one file / less file clutter. > Why can't versionable settings be treated like a wiki or ticket page and > versioned inside the repository itself rather than as a file in work area? > Then we can also see changes done to [versioned] settings right there in > timeline! > > Thinking of reasons... > 1) You may not want versioned settings, and keep with one file. > 2) The map to files is quite easy to use. Some people use, then, '.wiki' > files > in the repository instead of the usual wiki pages. > 3) The file interface offers most version capabilities currently, in > fossil. > Easier to reach old version, allowing branching, branches of code may need > different settings (ignore glob?). >
I have had this need many times. For example a build directory that must be ignored is moved. If I branch from the previous state and the ignores reflect the new state I now have irrelevant junk cluttering up my "fossil status". Hardly the end of the world but really a completely unnecessary annoyance. I am very much looking forward to this mechanism being a part of the official build. > 4) The versioned settings in files are *implemented* now. Having them ready > in > trunk should not annoy anyone who does not want to use them (if they > control the > repositories). > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
