On Thu, 08 Aug 2013 19:49:18 +0200, Richard Hipp <d...@sqlite.org> wrote:
On Thu, Aug 8, 2013 at 12:40 PM, Julian <j...@ptolserv.com> wrote:
One of the problems is that the help given by fossil help <command>
isn't
always complete. For example the help for checkin (fossil help ci),
doesn't
list the --date-override or --user-override options, even though they
appear to be accepted. The same appears to be the case for the branch
command.
The only way I've found to discover them is to use "grep find_option" on
the source - I'm not sure that is very user-friendly.
Two reasons for this.
(1) The help text is intended for quick reference and so we don't want to
clutter it up with lots of text describing obscure and rarely used
options.
I would politely disagree: the CL help should be complete, I believe.
at least for everything not considered experimental or "secret developer
features".
while git sure is over the top in this regard simply because there are too
much
options (I had a good laugh once when first looking at `git help log'), a
very positive
example for me is `hg': it's about as concise as `fossil' but complete as
far
as I can tell.
I know it is work and takes time and the current help is OK but sure
its not as complete as it should be in my view.
j.
(2) Some options we don't want people to use, either because they are
dangerous and likely to lead to problems, or because they are
experimental
and subject to change and perhaps untested, or perhaps the options are
deprecated and are still recognized purely for backwards compatibility.
The --date-override and --user-override options were put in place to
support scripts used to import Fossil content from other repository
formats. Both reasons (1) and (2) above apply to these options.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
