Ticket UUID: | d642c3621a9735a5ad4c583e72d496b091e8f481 | ||
Title: | Improve and update documentation | ||
Status: | Open | Type: | Documentation |
Severity: | Critical | Priority: | |
Subsystem: | Resolution: | ||
Last Modified: | 2009-11-10 14:55:00 | ||
Version Found In: | |||
Description & Comments: | |||
Hi Fossil Developers,
First of all I would like to thank you for FOSSIL, I think it is a great version control system (even though I am relatively new to version controlling). I am using Fossil for 2 months now, although I appreciate the underlying concepts, I think that the documentation is lacking. I need to do a lot of guess work and I believe this is penalizing Fossil. The documentation is, to my mind, a crucial and integral part of any software project. For example the page http://www.fossil-scm.org/index.html/doc/tip/www/reference.wiki is not very useful in its current stage: some commands are not explained, the ones that are explained are ambiguous (what's a VERSION?: I do not want to guess), it is not updated (I believe some commands have changed in between)... Some problems that I have run into: *The UPDATE command documentation is not clear (hopefully http://www.sqlite.org/privatebranch.html exists), *Nowhere it is explained that to close a leaf you need to do in the GUI. I was thinking that I can add a "closed" tag with the TAG command, *I have some files that I use only for testing, how can I ignore them when merging... Thanks in advance for your time. |