Re: Proposed patches/bugs etiquette?
María Scappini <[email protected]> Mon, 30 Mar 2026 13:28:32 -0300
| Newsgroups | gmane.comp.gnu.medical.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------FKnsH77Z1GaxMvFMfMqUxHml
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi, Karsten,
> I suggest you post a report when you don't find a solution
> within, say, two days.
Been reporting things faster these last few weeks, as instructed. :)
> 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".
Perfectly understood, also perfectly logical, and obvious in hindsight.
My path to (finally) get that was: I was stuck trying to fix things (couldn't
understand what was happening) -> then looked through the webpage for
guidance -> read the FAQ, specifically...
https://www.gnumed.de/documentation/GNUmedFAQ.html#HowReportBugs
... from there to this very useful article...
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
... realized that by trying to 'help' and delaying reports by
trying to fix them some way, I may have been delaying bug fixes.
So I thought it better to clarify and ask directly :)
(Also, from another link in How to Report Bugs section of the FAQ...
http://www.catb.org/~esr/faqs/smart-questions.html
... I laughed out loud:
"(...) If your mail program doesn't permit this,get a better mail program <http://linuxmafia.com/faq/Mail/muas.html>.
If your operating system doesn't support any e-mail programs that permit this,
/get a better operating system/." !!! Ha ha
... Another gem from there -- there were many parts that made me laugh:
"Q: I'm having problems with my Windows machine. Can you help?
A: Yes. Throw out that Microsoft trash and install an open-source operating
system like Linux or BSD."
Ha ha ha!! It's true!!)
> 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.
Will do so :)
Also, will activate turbo-mode-bugs-reports this week :O
Meaning: will use and test the master branch client (1.9.0 release candidate?)
as 'brutally' (?) as possible (weird actions, weird button-clicking, paths
I don't usually take...) and directly report any exceptions/unexpected
situations. In the hopes of being turbo-help (ha), and catch most stops
that happen with unusual user usage :D
Thank you for the guidance and patience, hope you have a great start of the week,
María
--------------FKnsH77Z1GaxMvFMfMqUxHml
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre>Hi, Karsten,</pre>
<blockquote type="cite"
cite="mid:[email protected]">
<pre wrap="" class="moz-quote-pre">I suggest you post a report when you don't find a solution
within, say, two days.</pre>
</blockquote>
<pre>Been reporting things faster these last few weeks, as instructed. :)</pre>
<blockquote type="cite"
cite="mid:[email protected]">
<pre wrap="" class="moz-quote-pre">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).</pre>
</blockquote>
<blockquote type="cite"
cite="mid:[email protected]">
<pre wrap="" class="moz-quote-pre">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".</pre>
</blockquote>
<pre>Perfectly understood, also perfectly logical, and obvious in hindsight.
My path to (finally) get that was: I was stuck trying to fix things (couldn't
understand what was happening) -> then looked through the webpage for
guidance -> read the FAQ, specifically...
<a class="moz-txt-link-freetext" href="https://www.gnumed.de/documentation/GNUmedFAQ.html#HowReportBugs">https://www.gnumed.de/documentation/GNUmedFAQ.html#HowReportBugs</a>
... from there to this very useful article...
<a class="moz-txt-link-freetext" href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">https://www.chiark.greenend.org.uk/~sgtatham/bugs.html</a>
... realized that by trying to 'help' and delaying reports by
trying to fix them some way, I may have been delaying bug fixes.
So I thought it better to clarify and ask directly :)
(Also, from another link in How to Report Bugs section of the FAQ...
<a class="moz-txt-link-freetext" href="http://www.catb.org/~esr/faqs/smart-questions.html">http://www.catb.org/~esr/faqs/smart-questions.html</a>
... I laughed out loud:
"(...) If your mail program doesn't permit this, <a class="ulink"
href="http://linuxmafia.com/faq/Mail/muas.html" target="_top">get a better mail program</a>.
If your operating system doesn't support any e-mail programs that permit this,
<i>get a better operating system</i>." !!! Ha ha
... Another gem from there -- there were many parts that made me laugh:
"Q: I'm having problems with my Windows machine. Can you help?
A: Yes. Throw out that Microsoft trash and install an open-source operating
system like Linux or BSD."
Ha ha ha!! It's true!!)
</pre>
<blockquote type="cite"
cite="mid:[email protected]">
<pre wrap="" class="moz-quote-pre">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.</pre>
</blockquote>
<pre>Will do so :)
Also, will activate turbo-mode-bugs-reports this week :O
Meaning: will use and test the master branch client (1.9.0 release candidate?)
as 'brutally' (?) as possible (weird actions, weird button-clicking, paths
I don't usually take...) and directly report any exceptions/unexpected
situations. In the hopes of being turbo-help (ha), and catch most stops
that happen with unusual user usage :D
Thank you for the guidance and patience, hope you have a great start of the week,
María
</pre>
</body>
</html>
--------------FKnsH77Z1GaxMvFMfMqUxHml--