On Sunday 17 July 2005 03:58, Paul Eggert wrote: > It is possible to fix the problem without creating an intervening "cat > -u"-like process as was done in the patch I just sent in. This can be > done by creating a pipe, redirecting ssh's stderr into this pipe, and > having cvs read from the pipe and write to stderr. I sketched out a > solution to this problem, enclosed below, but I haven't had time to > make it real (it doesn't work as written).
This is a solution that I suggested in reply to a discussion about my patch for this issue. Actually I use the solution for LinCVS to communicate with cvs (older versions without the patch) and since then never again have recognized any data loss and haven't received any user-bug-reports either, so it appears to be a reliable workaround. The drawback I see is errors reported via ssh-stderr might no more be serialized with ssh-stdout - but this seems to be of minor importance. Regards Frank -- - The LinCVS Team - http://www.lincvs.com _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
