I had fossil's parent process crash during a commit with autopush on.
$ fossil version
This is fossil version 1.20 [a75e2d2504] 2011-10-21 12:52:53 UTC
Subsequent 'fossil push' seems to have finished the job, and I don't see
anything unexpected or suspect any file corruption or anything like that.
However, in the directory that contains the local repo I now have two new
files:
[repo-name]-[big-long-number]-out.http
[repo-name]-[big-long-number]-in.http
-in is an empty file, and -out appears to be an http POST request, with a
file size significantly less than the Content-Length header suggests was
planned.
Is there any conceivable reason *not* to delete them and pretend this
never happened?
Thanks in advance,
--
Themba Fletcher
Description/Entity ...................... (tif@)descriptionentity.com
209-591-8096 ...................................... cell 317-435-6970
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
