Bug#131090: marked as done (scp: please enable -f option to fork to background)

Hello Collin,
thank you for sticking with me in this discussion. I am open to learning 
and really trying to understand DM behavior. Next beer is on me.

Am 02.06.2026 13:43 schrieb Colin Watson:
> On Tue, Jun 02, 2026 at 10:05:56AM +0000, [email protected] wrote:
>> Please don't throw the maintainer argument at me. There was no 
>> response for 24 years in this issue. So it seems to me that there is 
>> no active maintainer
> 
> Oh come on, this is just a bad-faith argument.
> ...
> I am human and have finite time, which I
> have to prioritize.

I am an upstream maintainer; not a DM for obviously reasons. ;)
Don't throw the free time argument. It is FOSS and your responsibility 
to manage your resources.  This also includes to see borders and 
restrictions and react to them. Don't use "time" as an excusse. This is 
not about fixing the issue but just reacting to it, review it and giving 
a direction for extern contributors.

There was no response to this ticket for 24 years. Sorry, but this is 
not acceptable, especially in your case where you seem to have been 
active in other tickets.

Even if this ticket would have gotten the lowest possible priority on 
your task list you should have been able to react on it in the time span 
of 24 years. You might be overloaded with work? Or your workflow need 
optimization? Or what else could be the reason that a ticket is 24 years 
without any response?

This is not Ubuntu, AntiX or any other distros. It is Debian and half of 
the other distros out there are derived from it. This comes with a 
responsibility.

> Having to spend time on this kind of argument doesn't help.

It helps to draw the boundaries of quality maintenance. I refuse to 
accept this dont-react-for-decades-but-ask-first-attitute.

> All you needed to do was ask first.

Sorry, but not after 24 years. This is not polite to me or the ticket 
opener.

So we agree that we disagree on some aspects about how maintenance 
should look like which tasks to prioritize.

Regards,
Christian Buhtz