[Dnsmasq-discuss] [PATCH] Fix potential memory leak
Geert Stappers
stappers at stappers.nl
Mon Mar 25 21:57:19 UTC 2024
On Mon, Mar 18, 2024 at 04:12:44PM +0000, Dan Schaper via Dnsmasq-discuss wrote:
> From "Brian Haley" <haleyb.dev at gmail.com> Date 3/18/2024 6:59:21 AM
>
> > > As an attempt to express that proposed patches get human attention.
> >
> > I'm not sure what that means...
The 'As an attempt to express that proposed patches get human attention'
means something like
The patch has been seen, it is not completely ignored.
> It means Geert doesn't think Simon is running `dnsmasq` to his (Geert's)
> liking so Geert is doing yet another passive aggressive attack on the list.
> You'll notice how Geert likes to change the email address he sends from with
> what he thinks are witty and creative names, like his monthly rules to post
> reminders.
>
> Would be nice to just blanket ban anything from @stappers.nl but until then
> it's easier to just set a rule to send anything from that address to spam.
>
> Geert has no authority to do anything in the `dnsmasq` project and this
> latest game with him setting up a patch repository is just a game. Simon is
> the sole gateway to getting any code in, much to Geert's dismay.
Yeah, the price of doing what is possible.
Shoving all and every dnsmasq task to Simon feels wrong.
Leaving proposed patches unanswered for days _is_ wrong.
In now three weeks am I the only one who made some effort to respond to
patch https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017464.html
and https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017473.html
Patches being ignored happened before and most likely will happen again.
Hence my experiment with dnsmasqmlpc, dnsmasq mailing list patch
collector. https://lists.sr.ht/~stappers/dnsmasqmlpc/patches
Groeten
Geert Stappers
--
Silence is hard to parse
More information about the Dnsmasq-discuss
mailing list