Dear Isaac:
Thanks for helping me through this. In fact, your discussion below triggered
the solution. It appears that I have been bitten by a PowerShell feature.
Piping data is not the same as in UNIX. When piping, unkown objects are treated
as text (at least in this case), and the text itself is converted to a .NET
array object before being sent out to the receiving program, at which point,
since the receiving program only accepts text (fossil) it will be reconverted
back into plain text, but this conversion adds the CRLF line endings instead of
the LF line endings that Git uses, thus rendering the data used by Git invalid.
There are a few solutions, but as it turns out, the easiest one for working
around this particular problem, since this is a one off, is to simply load up
cmd as a subshell and then do the processing from there, which works as
expected. Fossil works as intended if used from within Cmd for this piping.
All in all, I’m glad that this is a fairly straightforward issue. Thanks for
the help!
Yours truly,
Aaron W. Hsu
--
Aaron W. Hsu | arcf...@sacrideo.us | http://www.sacrideo.us
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
