On Mon, Jul 02, 2018 at 01:39:34PM +1200, Andrew Bartlett wrote: > We simply don't have the resources to manage the tasks you suggest
I'm saying one shouldn't send a message to nnnnn-close@bugs.d.o and instead just keep an existing bug open. That change alone actually conserves resources. Sending a message to the control bot to tag it upstream and perhaps mark it wontfix or a custom tag called triaged or something like that - doesn't sound particularly more taxing compared to closing. > Upstream (non-packaging) bugs filed here at best have to be copied into > Samba's bugzilla before any progress can be made and the lossy nature > of that just makes work for everyone. This is literally what every other maintainer is taught to do - weed through the chaff and forward upstream stuff upstream. > Finally, debates, even meta debates, about unsupported and ancient > Samba and MacOS versions are simply not productive. Yet, this isn't one, as I've long given up on expecting that upgrade path to be fixed - I've reverted to arguing simply that if there's a piece of functionality (Unix extensions) in the software, the documentation for the software should mention its basic characteristics, esp. those that have been known to cause annoying behavior in practice. It would be akin to having the Apache documentation describe its HTTPS support with two sentences in a manual, and have nothing else whatsoever (yet it ships e.g. /etc/apache2/mods-available/ssl.conf with a fair bit of info, and there's other docs too). -- 2. That which causes joy or happiness.