Micah Cowan <[EMAIL PROTECTED]> writes:

>> It just occurred to me that this change breaks backward compatibility.
>> It will break scripts that try to clean up after Wget or that in any
>> way depend on the current naming scheme.
>
> It may. I am not going to commit to never ever changing the current
> naming scheme.

Agreed, but there should be a very good reason for changing it, and
the change should be a clear improvement.  In my view, neither is the
case here.  For example, the change to respect the Content-Disposition
header constitutes a good reason[1].

Reply via email to