On May 23 12:23:25, cla...@xenei.com wrote:
> Given the level of support for the last few years, I think the code should
> be deprecated and removed in 2 major revisions.
> With few people to support the tool, there should be few sparkly bobbles to
> contend with. Keep the code to the main line.
>
Please don't send html emails to mailing lists.
On May 23 07:00:19, cary.le...@gmail.com wrote:
> dir="ltr">Keep the code in place. type="cite">On May 23, 2024, at 6:49 AM, Claude Warren
> wrote: type="cite">Given the level of support for the
> last few years, I think the c
Keep the code in place. On May 23, 2024, at 6:49 AM, Claude Warren wrote:Given the level of support for the last few years, I think the code should be deprecated and removed in 2 major revisions. With few people to support the tool, there should be few sparkly bobbles to contend with. Keep the
Given the level of support for the last few years, I think the code should
be deprecated and removed in 2 major revisions.
With few people to support the tool, there should be few sparkly bobbles to
contend with. Keep the code to the main line.
My vote (though I don't get one) is to deprecate now
On 5/23/24 10:26, Jan Stary wrote:
It is none of SoX's business to open network sockets
or spawn processes that make DNS queries and all that.
That may be true, but removing it would break any script that uses that
functionality, which is why non-backwards-compatible API changes are to
be av