Thomas Lussnig <[EMAIL PROTECTED]> writes:
> i think to add it on all source files is an bit of overkill.
But I was told that it was necessary for legal reasons, therefore it's
already been done.
> Because it is only mathers the point on using openssl on some
> operating systems. And on the oth
Yup, my mistake. I'll name the next prerelease pre3 to prevent
further confusion.
Ian Abbott <[EMAIL PROTECTED]> writes:
> The 1.8.2 branch is pretty similar to 1.8.1 at the moment and
> doesn't compile with any version of Borland C++.
Should we care to fix that before the release? I'm not sure how
important error-free compilation under Borland is.
Henrik van Ginhoven <[EMAIL PROTECTED]> writes:
> problem, I agree. On large networks some evil-minded person could
> write a tiny cron-script that ran once every 5 minutes or so to
> parse ps-output looking for nothing but passwords,
Note that the standard workaround for this problem, which is
Here is the final (ha ha) pre-test for the 1.8.2 bugfix release. Get
it from:
http://fly.srk.fer.hr/~hniksic/wget/wget-1.8.2-pre3.tar.gz
The difference between -pre1 is that the often reported Windows file
name problem has now been fixed.
Please try to compile it and see if it works for yo
Thanks; I've now applied it to the 1.8.2 branch.
>
>
>Note that the standard workaround for this problem, which is now even
>documented in the manual, is to use the `-i -' option. For example:
>
>wget -i -
>http://user:[EMAIL PROTECTED]/directory/file
>^D
>
>But I agree that's just a workaround. I'm now more open to the idea
>of introducing a
That is what I did, sorry for not making that clear. The question was
should I, in addition to that, also change COPYING, so that someone
who only reads that file can take notice of the exception?
>From the wording of your response I'd assume that the answer is "no".
I think you
