Hi Lukas, Are you subscribed to groff@gnu? I prefer not to mail both lists and people unless they express a preference for that (ideally via mail headers that communicate this, and if my MUA is clueful enough to interpret such indications).
At 2024-07-24T11:04:04+0200, Lukas Javorsky wrote: > I found multiple defects in Groff's source code, I'm sorry to hear that... > and I would like to help with fixing them by contributing several > commits. ...but this is happy news! > I didn't find much information about the contribution process on the > website [1], It sounds like you have bugs to report, so the "Bug Reports" section of the page you cited would describe an appropriate course to follow. >> Bug Reports >> >> Please report bugs using the bug tracker linked from the groff >> project page. Alternatively, but less preferably, you can use the >> form in the text file BUG-REPORT distributed with the groff source >> code; its purpose is to make sure that we have all the information we >> need to fix the bug. At the very least, read BUG-REPORT and make sure >> that you supply all the information that it asks for. Even if you are >> not sure that something is a bug, report it using BUG-REPORT: this >> will help us determine whether it really is a bug or not. > so I decided to ask here for more information. Could you please help > me figure out what is the preferred way for the contributions? I recommend you visit this link: https://savannah.gnu.org/bugs/?group=groff If you change the "query form" list box control from "Basic" to "Backlog" (which is what I use 99% of the time), you can perform a search based on several criteria, including keywords that appear in the bug summary. That will help you determine if the problem has already been reported (and, one hopes, fixed). If a search is unavailing, you can file a new report by clicking on the "Bugs" pop-up menu and selecting "Submit item", or by visiting this link: https://savannah.gnu.org/bugs/?group=groff&func=additem > Thank you so much for your help. I look forward to studying your reports! Regards, Branden
signature.asc
Description: PGP signature
