On Thu, Aug 15, 2013 at 11:12 AM, Joe Mistachkin <[email protected]>wrote:
> The command could be enhanced to allow that; however, not everything that > is allowed in the file format is surfaced via the command line interface. > i can second that - > In theory, the manifest parser needs to be able to cope with all "legal" > constructs, regardless of where they originate from (e.g. alternative > Fossil implementations, such as libfossil, external importers/exporters, > etc). > i've been using the fileformat.wiki as my main spec, but following manifest_parse() and manifest_crosslink() very closely, and i don't think i've built in anything which is incompatible with either the spec or the current code (i very much hope not! i'm scared to death of corrupting my repo here!). The cancel tag comments do "disappear" in some cases in the time because not all of the many code paths in manifest_crosslink() deal with, though. Here's my manifest_parse impl (on-going but mostly done): http://fossil.wanderinghorse.net/repos/f2/index.cgi/artifact/eed40d50e73cd12e17e540f8512b6ea114ca9054?ln=1684-2202 and here the crosslink: http://fossil.wanderinghorse.net/repos/f2/index.cgi/artifact/eed40d50e73cd12e17e540f8512b6ea114ca9054?ln=1252-1490 -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
