[Pkg-octave-devel] Bug#393495: octave-forge: help of leasqr need
improvements
Rafael Laboissiere
rafael at debian.org
Sun Oct 22 13:36:20 CEST 2006
* Francesco Potorti` <Potorti at isti.cnr.it> [2006-10-22 12:09]:
> >[BTW, Francisco, the next time please attach a stand-alone file with the
> >patch. It makes things easier.]
>
> What software do you use? Having text in line makes things easier for
> me and gives less problems on mailing lists.
Well, when I extracted the patch from the e-mail message, some white spaces
where changed such that the patch failed to apply. I had to edit it and add
it as an attachment in my last message. Your message arrived at my computer
with "Content-transfer-encoding: QUOTED-PRINTABLE", which is the encoding
scheme for the body of the message. If you look at actual mailbox file you
see things like this (wiht some characters escaped with "="):
--- leasqr.m~=092006-10-16 17:28:25.000000000 +0200
+++ leasqr.m=092006-10-16 17:48:43.000000000 +0200
@@ -22,24 +22,30 @@ function [f,p,kvg,iter,corp,covp,covr,st
% Levenberg-Marquardt nonlinear regression of f(x,p) to y(x).
%
% Version 3.beta
-% {}=3D optional parameters
-% x=3Dvec or mat of indep variables, 1 row/observation: x=3D[x0 x1..=
..xm]
The problem with your patch happened in some lines of leasqr.m that have
leading white spaces. For this reason, patches should always be attached
and never included inline in e-mail messages (unless it is sure that no
white-space issues are present).
--
Rafael
More information about the Pkg-octave-devel
mailing list