as a follow up on this (and the response to the original post by drh):
it _is_ bad that options like `--date-override' are not comprehensively
documented (notably with `commit') since they can be important for
"normal" users as well. e.g.:
accidentally, I'm just now in the somewhat painful process of extracting a
subset of files (and their revision history) from a rather big/old/messy
`hg' repository. the usual route would be to use `hg convert' plus a
filemap specification to generate a new `hg' repository containing only
the desired stuff then the rest would be easy (hg -> git -> fsl). alas!
this strategy does not allow to "flatten" the directory tree (in the old
repo the files are "way down" in some subdir, in the new one they should
be at the toplevel). retrospective `mv' actions than lead to problems
with diffing across the renames in fossil (at least this seems to be the
situation?). there where more problems with renames in the `hg' repo
not being handled too good in the whole conversion process -- at least I
could not achieve a satisfactory fossil repo in the end.
so what I did is I wrote a shell script collecting all relevant revisions
in the `hg' repo, updating in turn to each revision and committing the
`hg' working copy files to the new `fossil' repo directly. and here is the
catch: _only_ when using the --date-override flag (and knowing that it is
there is a prerequisite...) this can work sanely by extracting the date
from the `hg log' and inserting it correctly during the `fossil ci'
(instead of ending up with 100 commits within 10 seconds...)
just wanted to support julian in his opinion, that fossil's CL help should
strive to be complete. so, please augment information like the
one in question here if your time allows for this. I believe the user base
would appreciate this.
j.
On Thu, 08 Aug 2013 18:40:46 +0200, 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.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
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
