On Thu, 09 Jan 2014 22:01:07 +0100, Richard Hipp <d...@sqlite.org> wrote:
On Thu, Jan 9, 2014 at 3:54 PM, j. van den hoff
<veedeeh...@googlemail.com>wrote:
version 1.28 [6f1b5d6047] gives me memory faults when doing something
like
`fossil search whatever' #search pattern does not matter ...
when executing it on fossil's own timeline (i.e. in a checkout of the
`fossil' source code).
observed under MacOS 10.8.5.
it seems to be related to the length of the timeline. `search' works
just
fine for smaller projects.
can someone confirm this behaviour?
Confirmed. Fixed now. On trunk and on the 1.28 branch.
thanks for this. question: the output of `fossil search' is not
chronologically sorted. it should be in my view (top down, that is, from
new to old just as the timeline). is this intended behaviour?
another observation: I see strange hits in the search. e.g. (still for the
fossil timeline)
`fossil search abc' yields (upon others, obviously correct hits) a hit
for rev. 94694585cd which seemingly is a commit with an empty commit
message... looks like a bug to me.
--
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
--
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
