Stephan Beal wrote: > We'd be interested in hearing back if you discover how an error on your > end (if indeed it is) is confusing fossil into trying to read non-manifest > files as manifests.
Actually, your question sort of confuses me. From my (very tenuous) understanding of the code, it tries to read *every* incoming file during a sync as a manifest. It only takes further action if the file is successfully parsed as a manifest. This sort of thing leads to other kinds of confusion. For example, I took a snapshot of a 3rdparty repository. That 3rdparty repository itself includes a snapshot of the SQLite source tree, which had a manifest file in it. When I committed my snapshot, I suddenly saw an SQLite commit, complete with 'drh' as the committer, show up in own my project timeline! It corresponded to the data that was found in the manifest file. This supports my read of the code, I think. So the parse error is generated regardless -- the only question is whether it gets reported back to the pushing remote 'client'. That I guess is stimulated by my failing TH1 script. So Richard's change caused the true underlying cause of the error to propagate back to the client, not a 'harmless' parse error on a file that is not a manifest. But that is just my vague understanding: obviously Richard can comment more intelligently on that than I can. -- Eric A. Rubin-Smith Aterlo Networks, Inc. http://aterlo.com _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users