Re: Proposed patches/bugs etiquette?

Am Wed, Mar 18, 2026 at 05:40:01PM -0300 schrieb Mar=EDa Scappini:

> My question here is specifically:
> - do you prefer I report the bugs directly when they happen, full logs a=
ttached and description as usual...
> - ... or would you rather I spend a few days trying to patch things (alb=
eit not in the most ideal way), and
> THEN report the bug + what I think the cause is + the proposed fix?

Both ways are fine.

I suggest you post a report when you don't find a solution
within, say, two days.

The added benefit of a proposed solution is that it may, for
one thing, show other problems that needed workarounds for
the solution to work and, at the other hand, show what a
thinking process outside my own _wanted_ this to work (which
may be different from what I thought the code in question
ought to work).

I may also be in a better position to tell right away: "aah,
this bug is quite tricky, it touches upon this and that,
perhaps even conceptually".

So, by all means, try to find solutions, just don't hold
back "too long" :)    And if you don't want to work on a
given bug because it doesn't occur in code that's relevant
to your use case -- don't worry, post it.

Best regards,
Karsten
=2D-=20
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B