Ben, Thanks for providing improvements in fossil.
I'd like to share 2 comments: 1. Versioned settings: I'd prefer having all settings in a single text file with name="value" kind of one-setting-per-line format (although I don't mind a value spanning multiple lines for readability) rather than one file per setting. 2. Like many other users commented, I'd alo like relative path setting to be ON by default. I haven't tested your branch but would like to know if following would work: fossil commit -m "comment" ../parent.file ../parent/child.file local.file sub/file.name ... also for other commands like rm, add, etc. - Altu > ----- Original Message ----- > From: Ben Summers > Sent: 08/12/11 04:17 PM > To: fossil-users@lists.fossil-scm.org > Subject: [fossil-users] New features for merging > > Richard has kindly indicated he is probably willing to merge the changes in > the ben-testing branch if the community has no objections, after being asked > for any suggestions on improvements. > > I'd particularly like input on how these should be documented, and the names > chosen for settings and command line options. > > I've added: > > > * Versionable settings > > The inconvenience of using ignore-glob came up again a few days ago. When I > started using fossil, I couldn't quite work out how to use them sensibly. So, > I implemented "versionable" settings which take the values from versioned > files in the repository. For ignore-glob, it gives you the rough equivalent > of .gitignore files, although they're only specified at the root of the > repository in a .fossil-settings directory. > > Documentation: > - fossil help settings > - Settings page in the web UI > - http://fossil-scm.org/index.html/doc/ben-testing/www/settings.wiki > (linked from home page) > > > * SSL improvements > > I added support for SSL client certificates, for an extra level of > authentication to the server. In addition, I added a setting to specify the > trusted SSL root certificates. > > After implementing this, I was told of the existing jan-clientcert branch, > and feel a bit silly for not noticing it earlier. This implementation, > however, is much simpler and uses facilities built in to OpenSSL instead of > doing certificate management inside fossil. As such, the impact on the fossil > code is much less, but does require external programs to do the certificate > management. With those external programs, it can do everything that the > jan-clientcert branch does. > > Documentation: > - fossil help settings (ssl-identity, ssl-ca-location) > - fossil help clone (--ssl-identity option) > - error message when trying to clone a repo which requires a client cert > - http://fossil-scm.org/index.html/doc/ben-testing/www/ssl.wiki > (linked from home page and existing server instructions page) > > > * Relative pathname listings > > One of my projects requires that I work with the current working directory > inside a subdirectory of the repository. I found it a bit confusing to list > all filenames relative to the root of the repository, especially when copying > and pasting output of 'extras' to 'add'. > > I've added a "relative-paths" setting. This defaults to 'off', to avoid > changing the output for existing projects. Set this 'on' to list pathnames > relative to the current working directory for status, changes and extras > commands, with output similar to git's listings. > > You can also override this setting on the command line with the --rel-paths > and --abs-paths options. > > Documentation: > - fossil help settings (relative-paths) > - fossil help status / changes / extras (--rel-paths & --abs-paths options) > > Discussion on mailing list: > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05066.html > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05072.html > (although options etc have changed at Richard's suggestion) > > > * empty-dirs setting > > I moved to fossil from subversion, and my project expected the ability to > version empty directories. I think this has come up a couple of times on the > list. > > In an ideal world, I'd add the ability to version directories 'properly', but > it would be quite a large change to the internals. Taking a pragmatic > approach, I added a versionable empty-dirs setting which allows you to > specify a list of directories which should exist after a checkout. > > Documentation: > - fossil help settings > > > Thanks for any feedback. > > Ben > > > > -- > http://bens.me.uk/ > > > > _______________________________________________ > 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
